Vulnerability scanning
Every published version is assayed. With a feed loaded, vulnerability results come from that index. Without one, the assay still calls api.osv.dev.
Self-hosted · Rust
A lightweight Rust server. Metadata is in PostgreSQL. Bytes go to an S3-compatible bucket or to a directory. With S3, the FerroBox process does not keep the bytes. With the directory, the bytes are on a volume mounted into that same process. Zero JVM overhead. Vulnerability scanning, SBOMs, and signing ship in the same server.
PostgreSQL plus a byte store
Metadata is in PostgreSQL. Bytes go to an S3-compatible bucket or to a directory.
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 server, not bolted on after.
One server, all of these — with more ecosystems on the way.
Vulnerability scanning, SBOMs, signing, and access control are part of the same server as the registry itself.
Every published version is assayed. With a feed loaded, vulnerability results come from that index. Without one, the assay still calls api.osv.dev.
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.
OCI and Helm artifacts can be checked against a Cosign public key on pull and promote. That key is separate from the public key that signs the vulnerability index.
Block a client pull or a promotion when an artifact fails a CVE threshold, a license rule, or a Cosign check. If the known-vulnerability rule is on and the feed is missing, or that version's assay is not ready, the pull and the promote are denied.
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 captures from a running instance — the same UI you'd get after the quickstart below. Click one to see it larger.
Ecosystem chosen before create. Upstream is the public npm registry.
Its own page. Dataset 2026-10-03, Mode sync, reference ghcr.io/ferrobox/osv-db:2026-10-03.
The repository shows that dataset and a Manage link. lodash 4.17.20 shows [0 Crit | 2 High].
Status Ready against the 2026-10-03 index: 2 high, 3 medium, license MIT.
Known vulnerability at ≥ High. If that control is not Off, a missing feed or an assay that is not ready denies the pull.
A Mirror repo caching crates.io, with each version's size and digest.
Reader, Developer, and Admin, with the exact permission matrix.
Scoped read/write tokens for CI, independent of any login session.
Scope a team's repository access without per-user role juggling.
Metadata is in PostgreSQL. Bytes go to an S3-compatible bucket or to a directory. ./dev-up.sh starts PostgreSQL and Garage. ./dev-up.sh --filesystem is the smaller install: PostgreSQL and FerroBox only, with bytes on a volume mounted at /var/lib/ferrobox/blobs. The Helm chart stays PostgreSQL plus Garage unless storage.backend=filesystem and garage.enabled=false, with replicaCount 1. The 0.2.6 chart values set image.tag to 0.2.6, and the install sets the same tag.
git clone https://github.com/ferrobox/ferrobox.git
cd ferrobox/infra
./dev-up.shcd ferrobox/infra
./dev-up.sh --filesystemhelm install ferrobox oci://ghcr.io/ferrobox/charts/ferrobox --version 0.2.6 \
--namespace ferrobox --create-namespace \
--set image.tag=0.2.6helm install ferrobox oci://ghcr.io/ferrobox/charts/ferrobox --version 0.2.6 \
--namespace ferrobox --create-namespace \
--set image.tag=0.2.6 \
--set storage.backend=filesystem \
--set garage.enabled=false \
--set replicaCount=1The default login and how to stop the stack are in the Docker Compose quickstart. The vulnerability feed is in Concepts. The published image is ghcr.io/ferrobox/ferrobox:0.2.6. Pin it by digest: ghcr.io/ferrobox/ferrobox@sha256:5b1e9998912eba21cfbd455c7d27c44eba0639d222addc64138d4412bf33142f. That digest is the manifest list, linux/amd64 and linux/arm64. This image shows server version 0.2.6 on Settings and FerroBox v0.2.6 in the sidebar.
Clone it, self-host it, and see if it fits your setup.
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. Need it inside a competing product or service instead? That's a conversation, not a checkout — email [email protected].