One dated Sato Score reading per day. Days we changed the scoring method are marked. Not a safety or returns grade.
Score today
19
Change over 48d
0
Days measured
48
Days missed
0
Sato Score, daily
2026-09-23 → 2026-11-09
Every day in this span has a reading. A dashed vertical mark (┆) is a day Sato Hub changed the scoring method — movement on those days is ours, not the project’s.
What moved, component by component
Six charts, six axes — each scaled to its own maximum weight. They are never stacked on one axis: a component worth 10 points and one worth 35 would not be comparable on a shared scale, and the small one is usually the one that moved.
0% of 48 daily checks since 2026-09-23 succeeded. This is the share of OUR checks that succeeded. It is not uptime: a failed check can be on our side. When a check before 2026-09-01 failed, the checks before that date are left out of the rate: the probe counted a bot-block as a failure then and recorded no reason for any failure.
answered
host answered with an error
failed on our side
failed, unattributable
Every reading
The table the charts are drawn from. A missing day is missing from this table too — nothing is filled in.
Date
Score
Tier
Status
Our check
2026-11-09
19
Low
Active
inconclusive
2026-11-08
19
Low
Active
inconclusive
2026-11-07
19
Low
Active
inconclusive
2026-11-06
19
Low
Active
inconclusive
2026-11-05
19
Low
Active
inconclusive
2026-11-04
19
Low
Active
inconclusive
2026-11-03
19
Low
Active
inconclusive
2026-11-02
19
Low
Active
inconclusive
2026-11-01
19
Low
Active
inconclusive
2026-10-31
19
Low
Active
inconclusive
2026-10-30
19
Low
Active
inconclusive
2026-10-29
19
Low
Active
inconclusive
2026-10-28
19
Low
Active
inconclusive
2026-10-27
19
Low
Active
inconclusive
2026-10-26
19
Low
Active
inconclusive
2026-10-25
19
Low
Active
inconclusive
2026-10-24
19
Low
Active
inconclusive
2026-10-23
19
Low
Active
inconclusive
2026-10-22
19
Low
Active
inconclusive
2026-10-21
19
Low
Active
inconclusive
2026-10-20
19
Low
Active
inconclusive
2026-10-19
19
Low
Active
inconclusive
2026-10-18
19
Low
Active
inconclusive
2026-10-17
19
Low
Active
inconclusive
2026-10-16
19
Low
Active
inconclusive
2026-10-15
19
Low
Active
inconclusive
2026-10-14
19
Low
Active
inconclusive
2026-10-13
19
Low
Active
inconclusive
2026-10-12
19
Low
Active
inconclusive
2026-10-11
19
Low
Active
inconclusive
2026-10-10
19
Low
Active
inconclusive
2026-10-09
19
Low
Active
inconclusive
2026-10-08
19
Low
Active
inconclusive
2026-10-07
19
Low
Active
inconclusive
2026-10-06
19
Low
Active
inconclusive
2026-10-05
19
Low
Active
inconclusive
2026-10-04
19
Low
Active
inconclusive
2026-10-03
19
Low
Active
inconclusive
2026-10-02
19
Low
Active
inconclusive
2026-10-01
19
Low
Active
inconclusive
2026-09-30
19
Low
Active
inconclusive
2026-09-29
19
Low
Active
inconclusive
2026-09-28
19
Low
Active
inconclusive
2026-09-27
19
Low
Active
inconclusive
2026-09-26
19
Low
Active
inconclusive
2026-09-25
19
Low
Active
inconclusive
2026-09-24
19
Low
Active
inconclusive
2026-09-23
19
Low
Active
inconclusive
What happened alongside it
Releases, status changes, applied corrections and answered disputes, on the same dates — so a movement in the line can be read against an event rather than guessed at.
Sep 23, 2026
Listed on Sato Hub
Sep 23, 2026
Sato Hub began tracking this listing
How to read this
· Every point is one UTC day. A day we did not capture is drawn as a gap, never joined across.
· A change on a marked methodology day is ours, not the project’s.
· The score says how open, active and verifiable the project is. It is not a safety, quality or returns grade.
