Early signals · the misses
Where we were wrong
Flags we published that the outcome check decided against us stay on early signals and in the ledger either way. The candidates our own rules killed before publication are listed with the criterion each one missed, and by how much.
- Flags published
- 513every flag is written down when it is raised and stays counted
- Waiting for a verdict
- 299windows of 14 days that have not elapsed: not a miss yet
- Decided against us
- 15nothing happened inside the window, or Trending had already shown it
Flags that failed
A flag is only scored once its 14-day window has elapsed, so the next decision on a flag we published is due on 29 Oct 2026. Until then this panel is empty because no verdict exists, not because we were right.
Nothing happened inside the window (checked on 28 Oct 2026): it gained 108 stars in 7 days and never appeared on GitHub Trending. The top-100 cut of our own 7-day ranking that day was 2,225 stars, which is the number it would have had to beat.
Nothing happened inside the window (checked on 28 Oct 2026): it gained 1,825 stars in 7 days and never appeared on GitHub Trending. The top-100 cut of our own 7-day ranking that day was 2,225 stars, which is the number it would have had to beat.
Nothing happened inside the window (checked on 28 Oct 2026): it gained 192 stars in 7 days and never appeared on GitHub Trending. The top-100 cut of our own 7-day ranking that day was 2,225 stars, which is the number it would have had to beat.
Nothing happened inside the window (checked on 28 Oct 2026): it gained 192 stars in 7 days and never appeared on GitHub Trending. The top-100 cut of our own 7-day ranking that day was 2,225 stars, which is the number it would have had to beat.
Nothing happened inside the window (checked on 28 Oct 2026): it gained not recorded and never appeared on GitHub Trending. The top-100 cut of our own 7-day ranking that day was 2,225 stars, which is the number it would have had to beat.
Nothing happened inside the window (checked on 28 Oct 2026): it gained not recorded and never appeared on GitHub Trending. The top-100 cut of our own 7-day ranking that day was 2,225 stars, which is the number it would have had to beat.
Nothing happened inside the window (checked on 28 Oct 2026): it gained not recorded and never appeared on GitHub Trending. The top-100 cut of our own 7-day ranking that day was 2,225 stars, which is the number it would have had to beat.
Nothing happened inside the window (checked on 28 Oct 2026): it gained 368 stars in 7 days and never appeared on GitHub Trending. The top-100 cut of our own 7-day ranking that day was 2,225 stars, which is the number it would have had to beat.
Nothing happened inside the window (checked on 28 Oct 2026): it gained not recorded and never appeared on GitHub Trending. The top-100 cut of our own 7-day ranking that day was 2,225 stars, which is the number it would have had to beat.
Nothing happened inside the window (checked on 28 Oct 2026): it gained not recorded and never appeared on GitHub Trending. The top-100 cut of our own 7-day ranking that day was 2,225 stars, which is the number it would have had to beat.
Nothing happened inside the window (checked on 28 Oct 2026): it gained not recorded and never appeared on GitHub Trending. The top-100 cut of our own 7-day ranking that day was 2,225 stars, which is the number it would have had to beat.
Nothing happened inside the window (checked on 28 Oct 2026): it gained 1,209 stars in 7 days and never appeared on GitHub Trending. The top-100 cut of our own 7-day ranking that day was 2,225 stars, which is the number it would have had to beat.
Nothing happened inside the window (checked on 28 Oct 2026): it gained not recorded and never appeared on GitHub Trending. The top-100 cut of our own 7-day ranking that day was 2,225 stars, which is the number it would have had to beat.
Nothing happened inside the window (checked on 28 Oct 2026): it gained 50 stars in 7 days and never appeared on GitHub Trending. The top-100 cut of our own 7-day ranking that day was 2,225 stars, which is the number it would have had to beat.
Nothing happened inside the window (checked on 28 Oct 2026): it gained 175 stars in 7 days and never appeared on GitHub Trending. The top-100 cut of our own 7-day ranking that day was 2,225 stars, which is the number it would have had to beat.
Flags we killed before publishing
Measured on the score day 28 Oct 2026, using the same thresholds the flagging run uses. Each line passed every other condition of its rule and missed the one shown.
Accelerating (3 shown)
gained at least 200 stars in the last 7 days, at least 5× its own average week over the previous 26 weeks (weeks with no star history are ignored, and the average is floored at 10 stars/week so a repository that was flat does not divide by zero), with at least 8 weeks of history, and it has never appeared on GitHub Trending.
Accelerating: 557 stars in the last 7 days, 26 weeks of star history behind it. growth against its own average week measured 4.51× where at least 5.00× is needed, short by 0.49×.
Accelerating: 398 stars in the last 7 days, 17 weeks of star history behind it. growth against its own average week measured 4.39× where at least 5.00× is needed, short by 0.61×.
Accelerating: 575 stars in the last 7 days, 17 weeks of star history behind it. growth against its own average week measured 4.21× where at least 5.00× is needed, short by 0.79×.