FerroRepo - Rust-native Universal Artifact Repository

FerroRepo is a Rust-native universal artifact repository - a single self-contained server that stores and serves software packages across the major ecosystems and speaks the on-the-wire HTTP protocols of Sonatype Nexus Repository 3 and JFrog Artifactory, so existing build tools work unchanged. It runs as one process with no JVM and no external database to operate, persisting metadata to an embedded SQLite database and blobs to a local volume or to object storage, and it boots in well under a second on a small instance. A classic Nexus or Artifactory deployment needs a JVM, gigabytes of heap, and an external database before it serves a single artifact; FerroRepo's single-binary mode replaces that with one hardened binary that ships as a self-contained AMI.

What FerroRepo does today (v0.1.0): it serves 12 of 18 package protocols fully wired with in-tree conformance tests - Maven, npm, OCI / Docker Registry v2, PyPI (PEP 503 family), Cargo (sparse index), Go module proxy, Raw/Generic, NuGet v3, RubyGems (Compact Index), Helm (classic + OCI), APT, and YUM/DNF - plus a Nexus REST v1 and Artifactory-compatible admin surface. Storage is tiered (hot/warm/cold) with content-addressed blob de-duplication and pluggable S3 / GCS / Azure / MinIO blob backends via object_store. Authentication is on by default with a secure-by-default posture: anonymous reads are allowed (public-mirror friendly) while every write and admin action requires an authenticated principal with the right scope; built-in users, or federation to an external OIDC issuer, are supported, and a unique random admin password is generated on first boot. The supply-chain stack is real: SPDX and CycloneDX SBOMs, cosign keyless signing, and SLSA provenance are produced for releases.

Security and engineering posture is verifiable: every crate uses #![forbid(unsafe_code)], clippy runs clean at -D warnings (CI-enforced workspace-wide), there are zero unwrap() in production code, an SBOM is produced in CI, and continuous fuzzing runs against the parsers. The first-boot admin credential is newly generated and unique per instance (never a default or shared password) and is published to AWS Systems Manager Parameter Store as a SecureString by the provided CloudFormation / Terraform quick starts; the metadata volume is retained and encrypted at launch.

Honest scope: the supported topology is single-node (single-binary) with SQLite metadata on a durable EBS volume and the blob tier on S3; six rarer protocols (Conan, Conda, CRAN, Hex, CocoaPods, Bazel) are scope-declared and return 501 today; a horizontally scaled multi-node / Postgres-metadata topology is on the roadmap and is not yet supported - multi-node configurations are not deployed by the quick starts. This listing sells a hardened, scanned, supported distribution built from the Apache-2.0 source at a pinned release version; the code itself remains Apache-2.0. The AMI is metered automatically by AWS per running instance-hour, with no metering code in the product.