Package Registry
Create project-scoped repositories, publish immutable package versions, and give developers controlled access to install them.
What Packages is for
Use Clikkle Packages when a team needs a controlled npm distribution point for private SDKs, shared libraries and application packages. Repositories belong to an organization and project, while install and publish authority are separated by credential type.
- Group related packages in a project-scoped repository.
- Give developers and deployment systems read-only installation authority.
- Restrict publishing to maintainers or release automation.
- Preserve immutable released versions and release evidence.
How the service fits together
Console is the customer control plane for repository lifecycle and credentials. packages.clikkle.com serves package-manager traffic. api.packages.clikkle.com owns repository, release, integrity, provenance and audit state.
Was this page useful?