Score history
Bridge
Every Sato Hub Sato Score reading we have captured for this listing, one per day, each dated. Days we changed the scoring method are marked separately from days the project moved. How open, active and verifiable — not a safety, quality, or returns grade.
Score today
35
Change over 57d
+4
Days measured
57
Days missed
0
Sato Score, daily
2026-07-19 → 2026-09-13Every 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.
Every day the score moved
0 changes attributable to the project, 2 caused by a revision of the scoring method.
| Date | From | To | Change | Cause |
|---|---|---|---|---|
| 2026-09-01 | 32 | 35 | +3 | Sato Hub changed the scoring method |
| 2026-07-20 | 31 | 32 | +1 | Sato Hub changed the scoring method |
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.
The observed record
100% of Sato Hub's own daily checks succeeded over 57 checks. This is the share of OUR checks that succeeded. It is not uptime: a failed check can be on our side, and before 2026-09-01 no failure recorded why.
- 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-09-13 | 35 | Low | Active | up |
| 2026-09-12 | 35 | Low | Active | up |
| 2026-09-11 | 35 | Low | Active | up |
| 2026-09-10 | 35 | Low | Active | up |
| 2026-09-09 | 35 | Low | Active | up |
| 2026-09-08 | 35 | Low | Active | up |
| 2026-09-07 | 35 | Low | Active | up |
| 2026-09-06 | 35 | Low | Active | up |
| 2026-09-05 | 35 | Low | Active | up |
| 2026-09-04 | 35 | Low | Active | up |
| 2026-09-03 | 35 | Low | Active | up |
| 2026-09-02 | 35 | Low | Active | up |
| 2026-09-01 | 35 | Low | Active | up |
| 2026-08-31 | 32 | Low | Active | up |
| 2026-08-30 | 32 | Low | Active | up |
| 2026-08-29 | 32 | Low | Active | up |
| 2026-08-28 | 32 | Low | Active | up |
| 2026-08-27 | 32 | Low | Active | up |
| 2026-08-26 | 32 | Low | Active | up |
| 2026-08-25 | 32 | Low | Active | up |
| 2026-08-24 | 32 | Low | Active | up |
| 2026-08-23 | 32 | Low | Active | up |
| 2026-08-22 | 32 | Low | Active | up |
| 2026-08-21 | 32 | Low | Active | up |
| 2026-08-20 | 32 | Low | Active | up |
| 2026-08-19 | 32 | Low | Active | up |
| 2026-08-18 | 32 | Low | Active | up |
| 2026-08-17 | 32 | Low | Active | up |
| 2026-08-16 | 32 | Low | Active | up |
| 2026-08-15 | 32 | Low | Active | up |
| 2026-08-14 | 32 | Low | Active | up |
| 2026-08-13 | 32 | Low | Active | up |
| 2026-08-12 | 32 | Low | Active | up |
| 2026-08-11 | 32 | Low | Active | up |
| 2026-08-10 | 32 | Low | Active | up |
| 2026-08-09 | 32 | Low | Active | up |
| 2026-08-08 | 32 | Low | Active | up |
| 2026-08-07 | 32 | Low | Active | up |
| 2026-08-06 | 32 | Low | Active | up |
| 2026-08-05 | 32 | Low | Active | up |
| 2026-08-04 | 32 | Low | Active | up |
| 2026-08-03 | 32 | Low | Active | up |
| 2026-08-02 | 32 | Low | Active | up |
| 2026-08-01 | 32 | Low | Active | up |
| 2026-07-31 | 32 | Low | Active | up |
| 2026-07-30 | 32 | Low | Active | up |
| 2026-07-29 | 32 | Low | Active | up |
| 2026-07-28 | 32 | Low | Active | up |
| 2026-07-27 | 32 | Low | Active | up |
| 2026-07-26 | 32 | Low | Active | up |
| 2026-07-25 | 32 | Low | Active | up |
| 2026-07-24 | 32 | Low | Active | up |
| 2026-07-23 | 32 | Low | Active | up |
| 2026-07-22 | 32 | Low | Active | up |
| 2026-07-21 | 32 | Low | Active | up |
| 2026-07-20 | 32 | Low | Active | up |
| 2026-07-19 | 31 | Low | Active | up |
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.
- Jul 20, 2026Edited: deploy spec
- Jul 19, 2026Listed on Sato Hub
- Jul 19, 2026Sato 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.
- · The inputs behind today’s score are published at /api/export/score-inputs.json and the arithmetic is reproducible on your own machine.