# 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 ```sh sudo av install cask:trunk-io ``` Additional install commands: ### macOS - Homebrew Cask (100%): ```sh brew install --cask trunk-io ``` Evidence: local Homebrew cask metadata ## Package facts - **Package key:** cask:trunk-io - **Package manager:** Homebrew Cask - **Version:** 1.3.4 - **Source summary:** Developer experience toolkit used to check, test, merge, and monitor code - **Homepage:** - **Generated:** 2026-08-03T19:37:03+00:00 ## Executables - trunk (binary) - trunk (alias) ## Install behavior - Bottle: not available ## Freshness - Page generated: 2026-08-03 - Package-manager version: 1.3.4 ## 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. ### Sources - - - - - - ## Security Notes 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. ## 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 - Unix: .trunk/trunk.yaml ## Other Package-Manager Records - Nix - trunk-io: normalized package name match | nixpkgs package indexes: pkgs/by-name/tr/trunk-io/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - Nix - trunk: installed executable or alias match | nixpkgs package indexes: pkgs/by-name/tr/trunk/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - apk - trunk - 0.21.14-r0: installed executable or alias match | Alpine Linux edge package indexes: trunk from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz | Build, bundle & ship your Rust WASM application to the web | https://trunkrs.dev - dnf - trunk - 0.21.13-2.fc43: installed executable or alias match | Fedora Rawhide package metadata: trunk from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/repodata/07190dc5ae9f35ae73866675fed6d95fe6e8d9fe22c9d7cdf85862cb2ed24a4c-primary.xml.zst | Build, bundle & ship your Rust WASM application to the web | https://github.com/trunk-rs/trunk - pacman - trunk - 0.21.14-1: installed executable or alias match | Arch Linux sync databases: trunk from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz | Build, bundle & ship your Rust WASM application to the web | https://github.com/thedodd/trunk - Scoop - main/trunk: installed executable or alias match | Scoop official bucket manifest trees: bucket/trunk.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1 ## Combined YAML source View the package source record on GitHub. [combined/trunk-io.yml](https://github.com/mxcl/pkgdb/blob/main/combined/trunk-io.yml) ## Sources - pkg.so package database - curated configuration and credential file locations - curated package history - pkgdb category and tag curation - external package-manager database matches - cross-ecosystem install command graph