Cuitty Registry
npm, Cargo, PyPI, OCI.
npm, Cargo, PyPI, OCI · one indexscoped tokens, audit, proxy cacheemits → observe, code, safe, store
$ npm publish --registry https://registry.cuitty.acme.dev
@acme/core@2.4.1 published (npm protocol, SHA-512 integrity)
$ cui registry audit @acme/core --last 30d
47 installs, 3 publishes, 0 yanks
observe: registry.publish event emitted
Publish with the tools your build already uses
Standard protocol endpoints — no custom client required. Point your package manager at one registry URL. Packages default to private.
Tag a release in Code, and Registry publishes the artifact automatically. Every install, publish, and yank streams as an audit event to Observe.
npm
Full npm registry protocol. Scoped or unscoped packages, tarball hosting, version metadata, and search.
Cargo
Rust crate registry with git index or sparse protocol. Publish, yank, and search crates from Cargo directly.
PyPI
PEP 503 simple repository API. Upload with twine, install with pip or uv. Wheel and sdist support.
OCI / Docker
OCI distribution spec. Push and pull container images with Docker, Podman, or any OCI-compliant tool.
Your packages, on your storage
Registry is a standalone service. It does not require Cuitty Code. Blob and metadata storage go through Cuitty Store profiles — local SQLite for development, S3-compatible or managed for production.
Outbox-driven jobs handle index rebuilds, cleanup, and cross-region replication. SpiceDB-backed audit events log every publish, install, and access-policy change.
Operator controls and Code integration
Run Registry standalone with full operator controls, or pair it with Cuitty Code for repo provenance, release automation, and package visibility in the forge UI.
Operator controls
- Storage quotas and rate limits
- Scoped access tokens
- Audit event streaming
- Store profile configuration
With Cuitty Code
- Repo-linked provenance
- Release automation from tags
- Code App installs via registry
- Package visibility in the forge