pkg.soopen package index

cask / rank 1378

Install trunk-io with Homebrew Cask

Developer experience toolkit used to check, test, merge, and monitor code. Version 1.3.4 via Homebrew Cask; verified from local package data. Also installable with nix: nix profile install nixpkgs#trunk-io.

install

Additional install commands

macOS

Homebrew Caskverified · 100%
brew install --cask trunk-io

local Homebrew cask metadata

overview

Package summary

Developer experience toolkit used to check, test, merge, and monitor code

Commands and aliases

  • trunk

history

Project history and usage

Trunk is a developer-experience and CI reliability platform whose CLI is used to configure code quality checks, merge queues, flaky-test handling, and related workflow automation.

Project history

Trunk first presented Trunk Check in November 2021 as 'one linter to run them all': a repository-encoded way to standardize linters, analyzers, formatters, and local checks so teams did not have to maintain dozens of tools manually.

The platform expanded from code quality into broader CI and delivery reliability. Trunk Merge, announced in January 2024, focused on smarter merge queues that parallelize independent pull requests rather than forcing all work through a serial line.

Trunk's later documentation presents the platform around two scaling bottlenecks: merge queue serialization and flaky tests. Its public docs describe flaky-test detection, quarantine, merge queues, APIs, webhooks, Slack/Jira/Linear integrations, and a CLI that uploads test results and manages workflows.

Adoption history

Trunk's adoption story is enterprise-developer-tooling rather than a pure open-source CLI story. The website and docs emphasize teams using it to keep CI green, shorten merge waits, detect flaky tests, and standardize local code checks.

For package users, the Homebrew cask packages the launcher binary so developers can bootstrap the CLI consistently on macOS workstations and in setup scripts, while the service-backed pieces live behind Trunk accounts and organization configuration.

How it is used

In repositories, the CLI is commonly associated with .trunk/trunk.yaml configuration for code quality and actions, and with CI workflows that upload test artifacts or interact with merge queues.

Package-nerd usage centers on making the developer environment reproducible: install the trunk executable, check in the Trunk config, and let the tool manage the moving parts around lint, format, hooks, merge queues, and test reliability.

Why package nerds care

Trunk is significant because it is a meta-tool: it installs, pins, and coordinates other developer tools rather than being just one linter or formatter. That makes it interesting to people who care about package drift, hermetic installs, and repeatable local/CI behavior.

The cask also highlights a common modern packaging pattern: a proprietary or hosted developer platform exposes a small installable CLI, and Homebrew becomes the standard macOS distribution path.

Timeline

  • 2021-11-30: Trunk publishes Trunk Check as its first product for standardizing developer tooling.
  • 2024-01-03: Trunk publishes Trunk Merge for parallelized merge queues.
  • 2024-11-12: Trunk announces public beta for Flaky Tests.
  • 2026: Current docs position Trunk as a CI reliability platform around merge queues and flaky tests.

Related projects

  • GitHub Actions, GitLab CI, Jenkins, Buildkite, CircleCI, and Azure DevOps are supported CI surfaces in the docs.
  • GitHub native merge queue, Bors, Mergify, Datadog, and Buildkite Analytics appear as comparison points in Trunk materials.

security posture

No protected-tool coverage found yet

No matching local secret-handling manifest was found for trunk-io. Nucleus package metadata is still published here so future coverage has a stable package URL.

Install behavior

  • No Homebrew bottle metadata was recorded.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Unix
.trunk/trunk.yaml

executables

Installed executables

CommandKindExposureNote
trunkbinaryHomebrew cask binarytrunk

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-08-03
manager version1.3.4
manager updated
local dataunknown
upstreamnot available
latest detectednot detected
  • okNo freshness warnings were generated.

install metadata

Package metadata

Package keycask:trunk-io
Version1.3.4
Package managerHomebrew Cask
Homepagehttps://trunk.io/
SHA-25689fbdd8c7b63649eeb1479415757b898903c041e73b49b78028dbd64eca3087a
Download URLhttps://trunk.io/releases/launcher/1.3.4/trunk
Bottlenot recorded
Servicenone declared

source database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

Nix95%

trunk-io

nix profile install nixpkgs#trunk-io
  • normalized package name match
  • Matched by: Trunk Io
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/tr/trunk-io/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
Nix92%

trunk

nix profile install nixpkgs#trunk
  • installed executable or alias match
  • Matched by: Trunk
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/tr/trunk/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
apk92%

trunk 0.21.14-r0

Build, bundle & ship your Rust WASM application to the web

https://trunkrs.dev

sudo apk add trunk
  • License: MIT OR Apache-2.0
  • Architecture: x86_64
  • Source Package: trunk
  • 1 dependencies
  • 1 provides
  • installed executable or alias match
  • Matched by: Trunk
Alpine Linux edge package indexes · dl-cdn.alpinelinux.org · Alpine Linux edge package indexes: trunk from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz
dnf92%

trunk 0.21.13-2.fc43

Build, bundle & ship your Rust WASM application to the web

https://github.com/trunk-rs/trunk

sudo dnf install trunk
  • License: Apache-2.0 AND BSD-3-Clause AND BSL-1.0 AND CC0-1.0 AND ISC AND MIT AND MPL-2.0 AND (0BSD OR MIT OR Apache-2.0) AND (Apache-2.0 OR BSL-1.0) AND (Apache-2.0 OR
  • Category: Unspecified
  • Architecture: x86_64
  • Source Package: trunk
  • 6 dependencies
  • 2 provides
  • installed executable or alias match
  • Matched by: Trunk
Fedora Rawhide package metadata · dl.fedoraproject.org · Fedora Rawhide package metadata: trunk from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/repodata/07190dc5ae9f35ae73866675fed6d95fe6e8d9fe22c9d7cdf85862cb2ed24a4c-primary.xml.zst
pacman92%

trunk 0.21.14-1

Build, bundle & ship your Rust WASM application to the web

https://github.com/thedodd/trunk

sudo pacman -S trunk
  • License: Apache-2.0 AND MIT
  • Architecture: x86_64
  • 3 dependencies
  • installed executable or alias match
  • Matched by: Trunk
Arch Linux sync databases · geo.mirror.pkgbuild.com · Arch Linux sync databases: trunk from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz
Scoop92%

main/trunk

scoop install main/trunk
  • installed executable or alias match
  • Matched by: Trunk
Scoop official bucket manifest trees · api.github.com · Scoop official bucket manifest trees: bucket/trunk.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • pkg.so package database
  • pkgdb category and tag curation