One registry.
Every ecosystem.
npm, Go, Cargo, JVM, Maven, PyPI, NuGet, RubyGems, Composer, Dart, Zig, OCI and generic artifacts behind one URL and one token. Your tools keep working unchanged — built CI-first, ready for AI agents.
npm install -g @packr-registry/cliSixteen ecosystems, one registry
Every package format your team ships, served from one place your CI already knows how to talk to.
npm
The classic private npm registry — scoped packages, fine-grained tokens, and non-interactive CI auth.
npm install -g @packr-registry/cli
Go
A drop-in GOPROXY for private Go modules, with caching and quality scoring.
GOPROXY=https://api.packr.blueforge.studio
Cargo
A sparse-index registry for private Cargo crates.
[source.packr] registry = "sparse+https://api.packr.blueforge.studio"
JVM
JVM artifact hosting for Gradle and Maven builds via a /jvm/ repository.
repositories { maven("https://api.packr.blueforge.studio/jvm/") }Maven
Maven repository support for Java and Kotlin dependency resolution.
https://api.packr.blueforge.studio/maven/
PyPI
A PEP 503/691 compliant Python package index with twine publishing.
pip install -i https://api.packr.blueforge.studio/simple/ <pkg>
NuGet
A NuGet v3 feed with restore and push, compatible with the dotnet CLI.
dotnet nuget add source https://api.packr.blueforge.studio/nuget/v3/index.json -n packr
RubyGems
A RubyGems server for private gems — Bundler resolution via the compact index, `gem push` publishing.
gem push <pkg>-<version>.gem --host "https://api.packr.blueforge.studio"
Composer
A Packagist-compatible repository — point Composer's repositories config at packr and resolve through it.
composer config repositories.packr composer https://api.packr.blueforge.studio/composer/
Dart / Flutter
A pub.dev-compatible registry for Dart and Flutter — `dart pub` resolution, and the three-phase `dart pub publish` flow.
dart pub add mypkg --hosted-url=https://api.packr.blueforge.studio
Zig
Tarball hosting for Zig — `zig fetch` resolves against a version index, and `zig build` dependencies live on your own host.
zig fetch --save "https://api.packr.blueforge.studio/zig/mylib/0.1.0/source.tar.gz"
Swift / SwiftPM
Swift / SwiftPM registry (SE-0292) — `swift package-registry set` points a package at this host, and `.package(id:)` dependencies resolve through the registry instead of GitHub.
swift package-registry set https://api.packr.blueforge.studio/swift
Lua / LuaRocks
home.ecosystems.lua.description
luarocks install myrock --server https://api.packr.blueforge.studio/rocks
Conan (C++)
home.ecosystems.conan.description
conan remote add packr https://api.packr.blueforge.studio/conan && conan install --requires="zlib/1.3.1" -r packr
OCI / Helm
An OCI distribution registry at `/v2/` — `helm push`/`helm pull` and `docker push` round-trip charts and layers under the same authorization, visibility and credential scan as a package.
helm push mychart-0.1.0.tgz oci://api.packr.blueforge.studio/v2/
Generic artifacts
Raw artifacts that belong to no package — firmware, datasets, build outputs. `packr-cli publish-generic` uploads files per version, with channels for promoting a version without moving a byte.
packr-cli publish-generic acme/app@1.0.0 firmware.bin
Built for modern developers
Everything you need to run a private package registry in production — for npm, Go, Cargo, JVM, Maven, PyPI, NuGet, RubyGems, and Composer — without the enterprise bloat or the DIY pain.
Pull-through mirrors
Proxy and cache npmjs.org, crates.io, pypi.org, proxy.golang.org and Maven Central. One registry URL for everything; upstream outages serve stale, installs keep working.
config + doctor
`packr-cli config ‹eco› --write` points every toolchain at the registry; `packr-cli doctor` checks reachability, your token, and npm, Go, Cargo, PyPI, Maven and NuGet.
CI Auth
Token-based auth that Just Works. POST to login, get a JWT, use it anywhere. GitHub Action included.
Agentic-first
Quality scoring (0-100), capability search, package comparison, and dependency graphs for AI agents.
SQLite + Postgres + S3
SQLite for zero-config. Postgres for scale. Supabase or Backblaze B2 for tarball storage.
Webhooks
HMAC-signed webhook delivery for package.published, token.created, and other events.
Any Scope, Any Ecosystem
Use any npm scope or any registry protocol. Scoped tokens with read-only or publish-only permissions.
Dashboard + Themes
Package search with filters, webhook management, token analytics. Three themes: Default, Matrix, Pixel.
MCP + Agent SDK
Claude and Cursor can query your registry directly. TypeScript SDK for programmatic access.
Download Counts
Per-version download tracking, presigned S3 URLs for direct downloads, OpenAPI spec at /openapi.json.
Simple Deploy
One docker run command. Or docker-compose. Or the GitHub Action for one-step CI publish.
Free to Self-Host
Unlimited packages and scopes. No license key, no telemetry. Source-available.
Works in CI, Naturally
# .npmrc for your CI environment
@myorg:registry=https://api.packr.blueforge.studio
//api.packr.blueforge.studio/:_authToken=${PACKR_TOKEN}
# Publish from CI with just an env variable
npm publish --tag latest
# Or use the CLI for more control
packr publish --token ${PACKR_TOKEN}Simple, Transparent Pricing
Start free, scale as you grow
Your whole stack. One registry.
Spin up a private registry in minutes — no migration, no lock-in, no per-seat surprises.