For AI agents: the complete documentation index is available at /trace-index/llms.txt, the full documentation bundle is available at /trace-index/llms-full.txt, and this page is available as Markdown at /trace-index/how-to/install.md.

Install Trace Index

Trace Index publishes native binaries for x86-64 Linux, Intel macOS, and Apple Silicon macOS. Install the latest release without Rust or Cargo:

curl --proto '=https' --tlsv1.2 -fsSL \
  'https://github.com/wangyuxinwhy/trace-index/releases/latest/download/install.sh' | sh

Then confirm what was installed:

trace-index --version
trace-index docs list

The default destination is ~/.local/bin/trace-index. The installer never uses sudo; add that directory to PATH if needed.

Install one explicit version

Download the installer before passing options:

curl --proto '=https' --tlsv1.2 -fsSL \
  'https://github.com/wangyuxinwhy/trace-index/releases/latest/download/install.sh' \
  -o /tmp/trace-index-install.sh
sh /tmp/trace-index-install.sh --version 0.3.0 --bin-dir "$PWD/bin"

The script supports:

--version VERSION   install an explicit version instead of latest
--bin-dir DIR       install somewhere other than ~/.local/bin
--base-url URL      override the GitHub Releases root
--dry-run           resolve the target without downloading or changing files

It requires an absolute destination and HTTPS. Plain HTTP is accepted only with explicit --allow-http for the repository's local end-to-end test.

Each archive contains only trace-index and LICENSE. The installer downloads its sibling SHA-256 file, rejects unexpected archive paths, verifies that the binary reports the requested version, and then atomically replaces the destination.

Install from crates.io

With Rust 1.95 or newer:

cargo install trace-index --version 0.3.0 --locked
trace-index --version

cargo install compiles locally and can take longer than downloading a native release. Both installation paths provide the same CLI, bundled documentation, and public Schema.

Verify the installer locally

Repository maintainers can test the complete package, download, checksum, and installation path without publishing:

./scripts/test-installer.sh