Registry Overview
The DUUMBI registry is a package server that stores, indexes, and serves .tar.gz module archives. It provides both a REST API for the CLI client and a web interface for browsing and searching modules.
Public registry
Section titled “Public registry”The official public registry is available at registry.duumbi.dev. All @duumbi/* standard library modules are published here. No account is needed to browse or install modules — only publishing requires authentication.
Private registries
Section titled “Private registries”Teams can run their own registry instance for internal modules. The server ships as a single Docker image with SQLite storage — no external databases or services required.
See Self-Hosting for setup instructions.
How it works
Section titled “How it works”duumbi publish → .tar.gz + metadata → Registry API → SQLite + filesystemduumbi deps install → Registry API → .tar.gz download → .duumbi/cache/The registry stores module metadata (name, versions, integrity hashes) in SQLite and the actual archives on the filesystem. The CLI interacts with it through a versioned REST API (/api/v1/...).
API endpoints
Section titled “API endpoints”| Method | Endpoint | Auth | Description |
|---|---|---|---|
GET | /api/v1/modules/@scope/name | No | Module info (all versions) |
GET | /api/v1/modules/@scope/name/ver/download | No | Download .tar.gz |
PUT | /api/v1/modules/@scope/name | Bearer | Publish new version |
DELETE | /api/v1/modules/@scope/name/ver | Bearer | Yank version |
GET | /api/v1/search?q=text | No | Search modules |
GET | /health | No | Health check |
Next steps
Section titled “Next steps”- Using the Registry — search, install, and publish modules
- Authentication — accounts, tokens, and login flows
- Self-Hosting — run your own private registry