Eleven readings, taken every 4 hours.
Each one answers a question a repository page cannot. Counts are current as of the last run and come from the published bundles, so a reading sitting at zero says zero rather than disappearing.
What it measures
A zero is a measurement. It means the detector ran and nothing crossed its threshold, not that the reading is missing — /method says what each threshold is.
| Reading | The question it answers | Now | Counting |
|---|---|---|---|
| Live | What changed in the last few hours? | 4 | today |
| Ships | What released a new version? | 556 | releases |
| Forks | What is being copied faster than it usually is? | 98 | spikes |
| Demand | What are developers asking for in more than one place? | 165 | requests |
| Dependencies | What is being added, dropped, or jumped a major version? | 138 | shifts |
| Lineage | Which models say they were built on which? | 30 | claims |
| Model prices | What does a million tokens cost, and when did that change? | 415 | models |
| Outages | Does the thing I depend on go down, and how often? | 850 | incidents kept |
| Ecosystem | What do the registries, advisories and forums say, away from GitHub? | 271 | packages |
| Depended on | What does everything else quietly rely on? | 182 | packages read |
| This week | What would I have missed if I looked once a week? | — | — |
Where the numbers come from
The watchlist is curated and partial. Every page that counts from it says so.
417 repositories chosen by hand, plus 22 status feeds, 24 runtimes, 271 packages and 416 commit histories that have nothing to do with any watchlist.
How each reading is taken, and what it cannot do The published bundle