Artifact registry (apt, rpm, maven, pypi, npm, terraform) on top of any OCI registry
https://lajstrom.dev ↗// readme
Lajstrom
Artifact registry on top of any OCI registry.
One server, many repository formats: apt, rpm, maven, pypi, npm and raw files, and any OCI artifact through the facade. Every artifact is stored as an OCI artifact in the registry you already run: ECR, Harbor, Zot, GHCR, docker distribution. Lajstrom owns no bytes, only the index, and the index can always be rebuilt from the registry.
Lajstrom is Hungarian for “register, inventory”.
Clients keep their own protocol: pip, apt-get, mvn, npm and oras talk to Lajstrom as
to their usual repository, with no plugin. Each upload is checked, written to the registry and
indexed in SQLite or Postgres; lajstrom reindex rebuilds that index from the registry alone.
Users, tokens and per-repo roles live in Lajstrom; the registry only ever sees Lajstrom’s
credentials. v0.1.0 is planned for 2026-12-04 (roadmap).
https://lajstrom.dev
Install
No release is out yet. Until v0.1.0 (due 2026-12-04), build from source with Go 1.27:
git clone https://github.com/lajstrom/lajstrom.git && cd lajstrom
make build && bin/lajstrom version
From v0.1.0 on, the…