Skip to main content
Timoni is available as a binary executable for Linux, macOS and Windows. The AMD64 and ARM64 binaries can be downloaded from GitHub releases.
Install timoni on macOS or Linux with:
If you prefer to use the latest upstream binaries:
Note that the Homebrew formula will setup shell autocompletion for Bash, Fish and Zsh.

Shell autocompletion

Configure your shell to load timoni completions:
Add to your ~/.bashrc or ~/.bash_profile:
If you have an alias for timoni, you can extend shell completion to work with that alias:

Local cache

Timoni maintains a local cache of modules pulled from remote container registries. Cashing is meant to reduce network traffic for sequential pull operations and speeds up applying bundles which refer to modules with identical layers. The default cache location is $HOME/.timoni/cache and can be changed with either the --cache-dir global flag or TIMONI_CACHE_DIR environment variable. The global flag takes precedence over the environment variable. If the home directory is not writable, caching can be disabled by setting the TIMONI_CACHING=false environment variable.

SLSA Provenance & SBOMs

The build, release and provenance portions of Timoni’s supply chain meet the SLSA Build Level 3 requirements. The release artifacts are produced on GitHub-hosted runners using GoReleaser and the provenance generation is handled by the official SLSA GitHub Generator. To verify a release artifact such as the Timoni binary tarball, you can use the slsa-verifier tool:
The release artifacts are also attested with GitHub artifact attestations. To verify a release artifact with the GitHub CLI:
The Timoni GitHub Action performs the same verification before installing the binary on GitHub runners. Each release comes with a Software Bill of Materials (SBOM) in SPDX format. The SBOMs are generated on GitHub-hosted runners using GoReleaser and Syft. To scan a release for vulnerabilities, you can use Grype: