compare
Distribution vs Quay
The same facts for both, read from GitHub every night, and the relation a person reviewed.
| Fact | Distribution | Quay |
|---|---|---|
| Language | Go | Python |
| Licence | Apache-2.0 | Apache-2.0 |
| Stars | 11k | 2.8k |
| Latest | v3.1.2 | v3.17.5 |
| Last push | 2026-10-05 | 2026-10-06 |
| Release cadence | about 146 days between releases | about 5 days between releases |
| Active contributors | 16 commit authors on the default branch in the last 90 days | 32 commit authors on the default branch in the last 90 days |
| Flags | none | none |
How they relate
Both replace Docker Hub. Alternatives to Docker Hub →
PartialDistributionThe reference OCI registry server, without a web UI, users or scanning.
Full replacementQuayOrganisations, robot accounts, builds and vulnerability scanning with Clair.
Distribution
- v3.1.22026-09-24Welcome to the v3.1.2 release of registry!
- v3.1.12026-05-01Welcome to the v3.1.1 release of registry!
- v3.1.02026-04-06Welcome to the v3.1.0 release of registry!
- v3.0.02025-04-03Welcome to the v3.0.0 release of registry!
- v3.0.0-rc.42025-03-22Welcome to the v3.0.0-rc.4 release of registry!pre-release
Quay
- v3.17.52026-10-05[redhat-3.17] NO-ISSUE: fix(ci): pin s390x buildkit to v0.30.0 to avoid runc masking regression
- v3.16.62026-09-30[redhat-3.16] PROJQUAY-12275: chore(deps): upgrade pyasn1 from 0.6.3 to 0.6.4 to address CVE-2026-59885
- v3.14.92026-09-25[redhat-3.14] NO-ISSUE: fix(ci): use larger runner for build-and-publish multi-arch job
- v3.12.222026-09-11[redhat-3.12] NO-ISSUE: fix(ci): pin s390x buildkit to v0.30.0 to avoid runc masking regression
- v3.9.262026-09-09[redhat-3.9] NO-ISSUE: fix(ci): pin s390x buildkit to v0.30.0 to avoid runc masking regression
Distribution
✓ signed The latest release, v3.1.2, carries a signature GitHub verified.
Loading the security report
Quay
✓ signed The latest release, v3.17.5, carries a signature GitHub verified.
Loading the security report