Evidence Score
The score summarizes how much reviewable evidence is available. It does not mean a plugin is “86% compatible” and does not award points for tests the registry has not run.
Compatibility confidence
Registry install verified and Runtime verified are independent states. The disposable-profile install runner is connected in source; a count changes only after a schema-validated result is committed. Profile boot and capability smoke tests remain a stronger, separate layer.
Evidence freshness
Freshness never changes the historical result. It changes whether that result is safe to use as current upgrade evidence.
Manifest-aware classification
How the discovery number is counted
The 16,529 figure comes from one reproducible GitHub Search query, run daily and committed to this repository so any reading can be replayed.
The GitHub Topic web page and the Search API do not agree on a total for the same topic, and the gap moves in both directions as indexing catches up. Rather than pick whichever number looks better, this registry publishes the query, the source, and the date, so the figure can be checked against GitHub at any time.
Either way, the discovery number counts repositories carrying a tag. It is not a count of installable plugins, and the funnel above exists precisely because those two numbers are far apart.
Open data
Every reviewed record, the discovery funnel, and any live repository check are available as JSON under CC BY 4.0, with permissive CORS so other tools can consume them.
Important limits
Static signals cannot prove that a plugin is safe, future-compatible, or free from hidden behavior. Always review source, pin Git versions, and test in a disposable profile first.