Every number on this page is fetched live from the API when you load it. Nothing here is a screenshot, and nothing is written down in advance.
None of this is a vulnerability report. A CVE feed, a scanner and a bill-of-materials entry would all be unchanged by it: they describe what is in the product, not who is still working on it.
How to read it. Read the two question rows together: commit pace and release pace answer separately, and the gap between them is the information.
A single health score cannot say that a project commits rarely and ships every week. Two dated questions can.
Which of these is the quiet-but-shipping case, and which is the busy-but-rarely-shipping one, is a property of the numbers above on the day you load them, not of the packages.
The card above is fetched once and interpreted four times. The value is in what you do with the number, not in the number.
Tell us which one you are, or that none of them is: anteproof.com/support.
Every forecast is sealed with a public timestamp before the outcome and carries a receipt hash; the log's head is anchored daily to github.com/anteproof/log. The scored record is public, misses included.
And the maintenance families have no track record yet. Every past question was resolved against a
data feed we no longer trust, so the count and the score are withheld rather than published. The response
you just fetched says so itself, in calibration_note.withheld. The current state of every
family is on the calibration page and in
/v1/proof.
These are tracked and do not carry a forecast yet. The API resolves the package and says what is missing rather than erroring.
This list is a live query against a fixed set of well-known packages, run when you loaded the page. When it is empty it is not here at all.