The Community Edition Rodeo · fresh-first scanning · open rubric

The OSS Container Index

Benchmarking supply-chain trust across popular free software installations.

One grade per image, one publisher to trust per project, one digest that matches on every machine. Every number on this site decomposes to arithmetic you can audit — the raw grype JSON is a click away on every scanned image.

A green frog in a cowboy hat
157 projects indexed
142.1B pulls across all variants
137 scanned for CVEs
146 with Pulse score
27 at Pulse A or B

Where to go from here

The site has four doors. Each is one honest view of the same data.

157

Images

The daily index

Every Community-Edition image we track, with Security and Pulse grades you can filter, sort, and audit.

Browse →
24h

Trending

What agents reach for

Pulls, upvotes, and fresh releases, picked up as they happen. The signal, not the catalog.

See →
56

Publishers

Who signs the images

The ranked leaderboard of namespaces that ship Community-Edition images. One grade per publisher × project, 60-day window; v2 formula by default, v3 Wilson-corrected preview under ?variant=v3.

Rank →
JSON

API

Everything, machine-readable

Public endpoints for projects, images, grades, and the raw SBOM of any scan. Build it into your pipeline.

Docs →
For agent-led teams

Why start from a built image

Agents are fast at git clone. What they hand you a few minutes later is a build nobody else has seen: produced on one machine, from whatever the registries served that minute, with choices nobody wrote down. An image settles the six steps between source and running once, in the open.

A starting state, not a build

pull by digest is one step that either matches or doesn't. Building from source is dozens of steps that can each go differently on a different day, with a different toolchain, a different lockfile resolution, a different maintainer upstream.

Trust you can check

Signatures verified against a declared identity, SBOMs you can download, build provenance where the publisher ships it, and a dated grade whose arithmetic is on the page. Evidence your security team can inspect, not a vibe.

An open rubric, dated

Every grade is a formula with the ingredients listed: CVE count by severity, how fresh the image is, whether it declares a healthcheck, whether its signature verifies. The methodology page has the full changelog.

What goes into a grade

Two grades per image. Each one is arithmetic.

A Security
  • CVE count by severity (CVSS v3, bucketed Critical/High/Medium/Low)
  • Signature verifies against the publisher's declared identity
  • SBOM and build-provenance attestations present
  • HEALTHCHECK declared, non-root user where the product allows
  • Image rebuilt in the last 90 days
A Pulse
  • Upstream release cadence (how often the project ships)
  • Days since the image was first seen on ce.rodeo
  • Tag matches upstream's latest release (suffix-aware compare)
  • Number of maintainers and contributors signalled
  • Quality × breadth on the publisher, kept as separate columns

Trusted publishers

Full leaderboard →

Top of the quality-first ranking today. Operator-run accounts are unranked and labelled separately; the rest are compared on A/B product counts over 60 days.

Chainguard
A·10
10 products pushed · 13 tracked all-time
readystack
A·34 B·3 C·4 D·4 F·13
58 products pushed · 75 tracked all-time
11notes
A·9 F·7
16 products pushed · 22 tracked all-time
kong
A·2
2 products pushed · 3 tracked all-time

Start from a known state.

157 Community-Edition projects, graded today. Filter, sort, and search the catalog on the Images page.

Browse every image → Read the methodology