Sato Hub
BlockRun verification record

Score history

BlockRun

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

59

Change over 78d

+21

Days measured

78

Days missed

2

Sato Score, daily

2026-06-262026-09-13
02550751002026-07-14: Sato Hub changed the scoring method (39 → 52). Not a change by the project.2026-07-20: Sato Hub changed the scoring method (52 → 56). Not a change by the project.2026-09-01: Sato Hub changed the scoring method (56 → 59). Not a change by the project.2026-06-26: 38 (Low)2026-06-27: 38 (Low)2026-06-30: 38 (Low)2026-07-01: 39 (Low)2026-07-02: 39 (Low)2026-07-03: 39 (Low)2026-07-04: 39 (Low)2026-07-05: 39 (Low)2026-07-06: 39 (Low)2026-07-07: 39 (Low)2026-07-08: 39 (Low)2026-07-09: 39 (Low)2026-07-10: 39 (Low)2026-07-11: 39 (Low)2026-07-12: 39 (Low)2026-07-13: 39 (Low)2026-07-14: 52 (Medium)2026-07-15: 52 (Medium)2026-07-16: 52 (Medium)2026-07-17: 52 (Medium)2026-07-18: 52 (Medium)2026-07-19: 52 (Medium)2026-07-20: 56 (Medium)2026-07-21: 56 (Medium)2026-07-22: 56 (Medium)2026-07-23: 56 (Medium)2026-07-24: 56 (Medium)2026-07-25: 56 (Medium)2026-07-26: 56 (Medium)2026-07-27: 56 (Medium)2026-07-28: 56 (Medium)2026-07-29: 56 (Medium)2026-07-30: 56 (Medium)2026-07-31: 56 (Medium)2026-08-01: 56 (Medium)2026-08-02: 56 (Medium)2026-08-03: 56 (Medium)2026-08-04: 56 (Medium)2026-08-05: 56 (Medium)2026-08-06: 56 (Medium)2026-08-07: 56 (Medium)2026-08-08: 56 (Medium)2026-08-09: 56 (Medium)2026-08-10: 56 (Medium)2026-08-11: 56 (Medium)2026-08-12: 56 (Medium)2026-08-13: 56 (Medium)2026-08-14: 56 (Medium)2026-08-15: 56 (Medium)2026-08-16: 56 (Medium)2026-08-17: 56 (Medium)2026-08-18: 56 (Medium)2026-08-19: 56 (Medium)2026-08-20: 56 (Medium)2026-08-21: 56 (Medium)2026-08-22: 56 (Medium)2026-08-23: 56 (Medium)2026-08-24: 56 (Medium)2026-08-25: 56 (Medium)2026-08-26: 56 (Medium)2026-08-27: 56 (Medium)2026-08-28: 56 (Medium)2026-08-29: 56 (Medium)2026-08-30: 56 (Medium)2026-08-31: 56 (Medium)2026-09-01: 59 (Medium)2026-09-02: 59 (Medium)2026-09-03: 59 (Medium)2026-09-04: 59 (Medium)2026-09-05: 59 (Medium)2026-09-06: 59 (Medium)2026-09-07: 59 (Medium)2026-09-08: 59 (Medium)2026-09-09: 59 (Medium)2026-09-10: 59 (Medium)2026-09-11: 59 (Medium)2026-09-12: 59 (Medium)2026-09-13: 59 (Medium)3859592026-06-262026-09-13

2 days in this span have no reading; the line breaks there rather than joining across them. 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, 3 caused by a revision of the scoring method.

DateFromToChangeCause
2026-09-015659+3Sato Hub changed the scoring method
2026-07-205256+4Sato Hub changed the scoring method
2026-07-143952+13Sato Hub changed the scoring method
2026-07-013839+1the 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 & liveness20/35
35
Code transparency12/20
20
Interface verifiability0/10
10
Docs & demo6/10
10
Listing transparency & provenance14/15
15
Independent verification7/10
10

The observed record

100% of Sato Hub's own daily checks succeeded over 62 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.

2026-07-14: answered our check2026-07-15: answered our check2026-07-16: answered our check2026-07-17: answered our check2026-07-18: answered our check2026-07-19: answered our check2026-07-20: answered our check2026-07-21: answered our check2026-07-22: answered our check2026-07-23: answered our check2026-07-24: answered our check2026-07-25: answered our check2026-07-26: answered our check2026-07-27: answered our check2026-07-28: answered our check2026-07-29: answered our check2026-07-30: answered our check2026-07-31: answered our check2026-08-01: answered our check2026-08-02: answered our check2026-08-03: answered our check2026-08-04: answered our check2026-08-05: answered our check2026-08-06: answered our check2026-08-07: answered our check2026-08-08: answered our check2026-08-09: answered our check2026-08-10: answered our check2026-08-11: answered our check2026-08-12: answered our check2026-08-13: answered our check2026-08-14: answered our check2026-08-15: answered our check2026-08-16: answered our check2026-08-17: answered our check2026-08-18: answered our check2026-08-19: answered our check2026-08-20: answered our check2026-08-21: answered our check2026-08-22: answered our check2026-08-23: answered our check2026-08-24: answered our check2026-08-25: answered our check2026-08-26: answered our check2026-08-27: answered our check2026-08-28: answered our check2026-08-29: answered our check2026-08-30: answered our check2026-08-31: answered our check2026-09-01: answered our check2026-09-02: answered our check2026-09-03: answered our check2026-09-04: answered our check2026-09-05: answered our check2026-09-06: answered our check2026-09-07: answered our check2026-09-08: answered our check2026-09-09: answered our check2026-09-10: answered our check2026-09-11: answered our check2026-09-12: answered our check2026-09-13: answered our check
  • 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-09-1359MediumActiveup
2026-09-1259MediumActiveup
2026-09-1159MediumActiveup
2026-09-1059MediumActiveup
2026-09-0959MediumActiveup
2026-09-0859MediumActiveup
2026-09-0759MediumActiveup
2026-09-0659MediumActiveup
2026-09-0559MediumActiveup
2026-09-0459MediumActiveup
2026-09-0359MediumActiveup
2026-09-0259MediumActiveup
2026-09-0159MediumActiveup
2026-08-3156MediumActiveup
2026-08-3056MediumActiveup
2026-08-2956MediumActiveup
2026-08-2856MediumActiveup
2026-08-2756MediumActiveup
2026-08-2656MediumActiveup
2026-08-2556MediumActiveup
2026-08-2456MediumActiveup
2026-08-2356MediumActiveup
2026-08-2256MediumActiveup
2026-08-2156MediumActiveup
2026-08-2056MediumActiveup
2026-08-1956MediumActiveup
2026-08-1856MediumActiveup
2026-08-1756MediumActiveup
2026-08-1656MediumActiveup
2026-08-1556MediumActiveup
2026-08-1456MediumActiveup
2026-08-1356MediumActiveup
2026-08-1256MediumActiveup
2026-08-1156MediumActiveup
2026-08-1056MediumActiveup
2026-08-0956MediumActiveup
2026-08-0856MediumActiveup
2026-08-0756MediumActiveup
2026-08-0656MediumActiveup
2026-08-0556MediumActiveup
2026-08-0456MediumActiveup
2026-08-0356MediumActiveup
2026-08-0256MediumActiveup
2026-08-0156MediumActiveup
2026-07-3156MediumActiveup
2026-07-3056MediumActiveup
2026-07-2956MediumActiveup
2026-07-2856MediumActiveup
2026-07-2756MediumActiveup
2026-07-2656MediumActiveup
2026-07-2556MediumActiveup
2026-07-2456MediumActiveup
2026-07-2356MediumActiveup
2026-07-2256MediumActiveup
2026-07-2156MediumActiveup
2026-07-2056MediumActiveup
2026-07-1952MediumActiveup
2026-07-1852MediumActiveup
2026-07-1752MediumActiveup
2026-07-1652MediumActiveup
2026-07-1552MediumActiveup
2026-07-1452MediumActiveup
2026-07-1339LowActivenot checked
2026-07-1239LowActivenot checked
2026-07-1139LowActivenot checked
2026-07-1039LowActivenot checked
2026-07-0939LowActivenot checked
2026-07-0839LowActivenot checked
2026-07-0739LowActivenot checked
2026-07-0639LowActivenot checked
2026-07-0539LowActivenot checked
2026-07-0439LowActivenot checked
2026-07-0339LowActivenot checked
2026-07-0239LowActivenot checked
2026-07-0139LowActivenot checked
2026-06-3038LowActivenot checked
2026-06-2738LowActivenot checked
2026-06-2638LowActivenot checked

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. Jul 14, 2026
    Enriched: creator name, supported integrations, tags, agent type
  2. Jul 14, 2026
    Sato Score tier: Low → Medium
    Score 39 → 52.
  3. Jul 1, 2026
    Auto-enriched: has pricing
  4. Jun 26, 2026
    Sato Hub began tracking this listing
  5. Jun 25, 2026
    Listed on Sato Hub

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.