Overview Preview
Active Development
The Zena package manager and registry are under active development. Commands, manifest fields, and lexicon schemas may change as the system matures.
Zena packages are libraries and tools for the Zena programming language. Add one to your project with zena pkg add, and publish your own with zena pkg publish.
Install a package ​
Add a package by its scope:name:
zena pkg add acme:router
Then import its libraries by that name:
import {Router} from 'acme:router/server';
zena pkg add records the package in zena-package.json and pins the exact release in zena-lock.json, so every machine builds the same code. See Installing Packages.
Publish a package ​
Sign in with your Bluesky or other AT Protocol account, create a scope once, and publish:
zena pkg login alice.bsky.social
zena pkg scope create acme
zena pkg publish --scope acme
See Publishing Packages, and Defining a Package for what goes in zena-package.json.
Security ​
Every dependency is pinned by its content hash, a published version never changes, and a package can require several maintainers to approve each release. See Security.
Scopes, organizations and teams ​
Packages are published under a scope, such as acme, whose owners and publishers create its packages. A scope can be upgraded to an organization, with members and teams, and who belongs stays private until they act. See Scopes, Orgs & Teams.
Decentralized ​
No single registry owns your packages: each keeps its own identity and data wherever it is hosted, and the projects that depend on it name it by that identity. The package manager is built on the AT Protocol, the network Bluesky runs on. See Decentralized Packages.
Documentation guide ​
| Section | Topics covered |
|---|---|
| Installing Packages | Setting up a project, adding dependencies, importing libraries, updating, and fetching |
| Workspaces & Lockfiles | Multi-package workspaces, path dependencies, version selection, and zena-lock.json |
| Publishing Packages | Signing in, creating scopes, publishing releases, approving held releases, and retracting versions |
| Defining a Package | zena-package.json fields, exports, virtual targets, and dependency types |
| Security | Pinned hashes, immutable versions, maintainer approvals, automation accounts, and what is planned |
| Approvals & Policies | Release approvals, thresholds, scope policies, and CI automation accounts |
| Scopes, Orgs & Teams | Scope maintainers, organizations, teams, package maintainers, and private memberships |
| Decentralized Packages | Package identity, owning your data, mirrors and indexes, and labels |
| AT Protocol Architecture | DIDs, handles, repository records, dev.zena-lang.* lexicons, and source archives |
| CLI Commands | Subcommands, flags, and environment variables for zena |