Sato Hub
Score history

Orthogonal

One dated Sato Score reading per day. Days we changed the scoring method are marked. Not a safety or returns grade.

Score today

34

Change over 48d

+10

Days measured

48

Days missed

0

Sato Score, daily

2026-09-23 → 2026-11-09
02550751002026-09-23: 24 (Low)2026-09-24: 24 (Low)2026-09-25: 24 (Low)2026-09-26: 24 (Low)2026-09-27: 24 (Low)2026-09-28: 24 (Low)2026-09-29: 24 (Low)2026-09-30: 24 (Low)2026-10-01: 34 (Low)2026-10-02: 34 (Low)2026-10-03: 34 (Low)2026-10-04: 34 (Low)2026-10-05: 34 (Low)2026-10-06: 34 (Low)2026-10-07: 34 (Low)2026-10-08: 34 (Low)2026-10-09: 34 (Low)2026-10-10: 34 (Low)2026-10-11: 34 (Low)2026-10-12: 34 (Low)2026-10-13: 34 (Low)2026-10-14: 34 (Low)2026-10-15: 34 (Low)2026-10-16: 34 (Low)2026-10-17: 34 (Low)2026-10-18: 34 (Low)2026-10-19: 34 (Low)2026-10-20: 34 (Low)2026-10-21: 34 (Low)2026-10-22: 34 (Low)2026-10-23: 34 (Low)2026-10-24: 34 (Low)2026-10-25: 34 (Low)2026-10-26: 34 (Low)2026-10-27: 34 (Low)2026-10-28: 34 (Low)2026-10-29: 34 (Low)2026-10-30: 34 (Low)2026-10-31: 34 (Low)2026-11-01: 34 (Low)2026-11-02: 34 (Low)2026-11-03: 34 (Low)2026-11-04: 34 (Low)2026-11-05: 34 (Low)2026-11-06: 34 (Low)2026-11-07: 34 (Low)2026-11-08: 34 (Low)2026-11-09: 34 (Low)2434342026-09-232026-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.

Every day the score moved

1 change attributable to the project, 0 caused by a revision of the scoring method.

DateFromToChangeCause
2026-10-012434+10the project

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.

Maintenance & liveness8/35
35
Code transparency0/20
20
Interface verifiability0/10
10
Docs & demo10/10
10
Listing transparency & provenance12/15
15
Independent verification4/10
10

The observed record

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.

2026-09-23: failed on our side — not attributable to the project2026-09-24: failed on our side — not attributable to the project2026-09-25: failed on our side — not attributable to the project2026-09-26: failed on our side — not attributable to the project2026-09-27: failed on our side — not attributable to the project2026-09-28: failed on our side — not attributable to the project2026-09-29: failed on our side — not attributable to the project2026-09-30: failed on our side — not attributable to the project2026-10-01: failed on our side — not attributable to the project2026-10-02: failed on our side — not attributable to the project2026-10-03: failed on our side — not attributable to the project2026-10-04: failed on our side — not attributable to the project2026-10-05: failed on our side — not attributable to the project2026-10-06: failed on our side — not attributable to the project2026-10-07: failed on our side — not attributable to the project2026-10-08: failed on our side — not attributable to the project2026-10-09: failed on our side — not attributable to the project2026-10-10: failed on our side — not attributable to the project2026-10-11: failed on our side — not attributable to the project2026-10-12: failed on our side — not attributable to the project2026-10-13: failed on our side — not attributable to the project2026-10-14: failed on our side — not attributable to the project2026-10-15: failed on our side — not attributable to the project2026-10-16: failed on our side — not attributable to the project2026-10-17: failed on our side — not attributable to the project2026-10-18: failed on our side — not attributable to the project2026-10-19: failed on our side — not attributable to the project2026-10-20: failed on our side — not attributable to the project2026-10-21: failed on our side — not attributable to the project2026-10-22: failed on our side — not attributable to the project2026-10-23: failed on our side — not attributable to the project2026-10-24: failed on our side — not attributable to the project2026-10-25: failed on our side — not attributable to the project2026-10-26: failed on our side — not attributable to the project2026-10-27: failed on our side — not attributable to the project2026-10-28: failed on our side — not attributable to the project2026-10-29: failed on our side — not attributable to the project2026-10-30: failed on our side — not attributable to the project2026-10-31: failed on our side — not attributable to the project2026-11-01: failed on our side — not attributable to the project2026-11-02: failed on our side — not attributable to the project2026-11-03: failed on our side — not attributable to the project2026-11-04: failed on our side — not attributable to the project2026-11-05: failed on our side — not attributable to the project2026-11-06: failed on our side — not attributable to the project2026-11-07: failed on our side — not attributable to the project2026-11-08: failed on our side — not attributable to the project2026-11-09: failed on our side — not attributable to the project
  • 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.

DateScoreTierStatusOur check
2026-11-0934LowActiveinconclusive
2026-11-0834LowActiveinconclusive
2026-11-0734LowActiveinconclusive
2026-11-0634LowActiveinconclusive
2026-11-0534LowActiveinconclusive
2026-11-0434LowActiveinconclusive
2026-11-0334LowActiveinconclusive
2026-11-0234LowActiveinconclusive
2026-11-0134LowActiveinconclusive
2026-10-3134LowActiveinconclusive
2026-10-3034LowActiveinconclusive
2026-10-2934LowActiveinconclusive
2026-10-2834LowActiveinconclusive
2026-10-2734LowActiveinconclusive
2026-10-2634LowActiveinconclusive
2026-10-2534LowActiveinconclusive
2026-10-2434LowActiveinconclusive
2026-10-2334LowActiveinconclusive
2026-10-2234LowActiveinconclusive
2026-10-2134LowActiveinconclusive
2026-10-2034LowActiveinconclusive
2026-10-1934LowActiveinconclusive
2026-10-1834LowActiveinconclusive
2026-10-1734LowActiveinconclusive
2026-10-1634LowActiveinconclusive
2026-10-1534LowActiveinconclusive
2026-10-1434LowActiveinconclusive
2026-10-1334LowActiveinconclusive
2026-10-1234LowActiveinconclusive
2026-10-1134LowActiveinconclusive
2026-10-1034LowActiveinconclusive
2026-10-0934LowActiveinconclusive
2026-10-0834LowActiveinconclusive
2026-10-0734LowActiveinconclusive
2026-10-0634LowActiveinconclusive
2026-10-0534LowActiveinconclusive
2026-10-0434LowActiveinconclusive
2026-10-0334LowActiveinconclusive
2026-10-0234LowActiveinconclusive
2026-10-0134LowActiveinconclusive
2026-09-3024LowActiveinconclusive
2026-09-2924LowActiveinconclusive
2026-09-2824LowActiveinconclusive
2026-09-2724LowActiveinconclusive
2026-09-2624LowActiveinconclusive
2026-09-2524LowActiveinconclusive
2026-09-2424LowActiveinconclusive
2026-09-2324LowActiveinconclusive

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.

  1. Oct 1, 2026
    Auto-enriched: has pricing, supported integrations, deployment options, has demo
  2. Sep 23, 2026
    Listed on Sato Hub
  3. 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.
  • · The inputs behind today’s score are published at /api/export/score-inputs.json and the arithmetic is reproducible on your own machine.
← Verification recordThis week’s moversDispute this score