Vulnerability scanning
Every artifact is checked against OSV as it's pushed, so known CVEs surface before they reach a build.
Self-hosted · one Rust binary
FerroBox is a single self-hosted binary for Cargo, npm, PyPI, OCI/Docker, Helm, Conan, Maven, NuGet, Go, and generic artifacts — with vulnerability scanning, SBOMs, and signing built in, not bolted on.
One binary
Deploy a single Rust binary instead of a pile of separate registry apps.
One login
SSO and RBAC apply across every ecosystem — no per-tool credentials to juggle.
Security built in
Vulnerability scanning, SBOMs, and signing ship with the binary, not bolted on after.
One binary. Ten ecosystems. No exceptions.
Supply-chain security and registry ops that usually mean bolting on separate scanners, signers, and policy engines — built into the binary you already run.
Every artifact is checked against OSV as it's pushed, so known CVEs surface before they reach a build.
A CycloneDX SBOM is generated for every artifact automatically — no separate pipeline step to remember or maintain.
Flag incompatible or risky licenses in your dependency tree before they end up in a shipped artifact.
Artifacts are signed on the way in and verifiable on the way out — supply-chain integrity without extra tooling.
Block downloads or promotions outright when an artifact fails a CVE severity threshold or a license rule.
Host your own artifacts (Forge), pull-through cache upstreams (Mirror), or aggregate several repos behind one virtual endpoint (Alloy).
Keep multiple FerroBox instances in sync across sites or regions for redundancy and locality.
OIDC single sign-on for people, fine-grained roles per repo, and scoped robot tokens for CI — no shared admin credentials.
Make releases immutable, cap storage per repo, and let garbage collection clean up what your retention rules don't need anymore.
Plus webhooks and a full audit trail for everything that happens in the registry.
Real screenshots are on the way — these are layout sketches so you can picture the shape of the UI in the meantime.
FerroBox ships as a container image and a Helm chart forv0.1.0.
docker pull ghcr.io/ferrobox/ferrobox:0.1.0helm install ferrobox oci://ghcr.io/ferrobox/charts/ferrobox --version 0.1.0Full configuration reference (Postgres, S3-compatible storage, OIDC, admission policies, and more) lives in theproduct README.
Clone it, self-host it, and see how far one binary gets you.
FerroBox is source-available under the Functional Source License 1.1, Apache 2.0 Future License (FSL-1.1-Apache-2.0) — free for internal use, and each release becomes Apache-2.0 two years after it ships.