Homebrew
brew tap zed-pkg/tap brew install zed-pkg zed --version
From repository to verified package.
Zed coordinates package artifacts across ecosystems while your source repository remains the provenance anchor. Start with the CLI, exercise the package locally, then publish only the files consumers need.
Install the CLI
The Homebrew tap is the documented binary install path. Building from source remains available for contributors and pinned internal builds.
Build from source
git clone https://github.com/zed-pkg/zed-cli cd zed-cli cargo install --path .
Binary-name note
The Zed editor also ships a zed command. Install this CLI
under a separate prefix or shell alias when both tools share a machine.
Author one package contract
Every authored package is identified as org/name and starts
with a repository-root .zpkg.toml. The CLI validates this
manifest offline before publication.
[package] org = "acme" name = "http-kit" version = "0.1.0" license = "MIT" [package.repository] vcs = "git" url = "https://github.com/acme/http-kit" [install] dir = "zed_modules" adapter = "none"
1. Initialize
zed init --org acme writes the starting manifest in the current package repository.
2. Validate
zed validate checks the manifest and optional lock without network access or mutation.
3. Round-trip
zed r2g packs and consumes the artifact through an isolated file registry before release.
Publish, then consume exactly
Publisher flow
git tag v0.1.0 zed r2g zed publish
Normal publication verifies a clean worktree and a matching version tag, packs the pruned artifact, writes registry metadata, and mirrors supported GitHub repositories.
Consumer flow
zed add acme/http-kit@^0.1 zed install zed install --frozen
The first install resolves and records content identity. Frozen installs replay the lock and fail rather than silently selecting a different artifact.
Choose the install shape
| Mode | Use it for | Materialization |
|---|---|---|
symlink | Developer workstations and repeated local projects | One content-addressed store, linked into zed_modules/ |
copy | OCI layers, build contexts, and read-only runtime images | Self-contained project files copied from the verified store |