Sato Hub
CloddsBot verification record

Score history

CloddsBot

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

75

Change over 86d

+42

Days measured

86

Days missed

4

Sato Score, daily

2026-06-162026-09-13
02550751002026-06-17: Sato Hub changed the scoring method (33 → 54). Not a change by the project.2026-06-25: Sato Hub changed the scoring method (55 → 69). Not a change by the project.2026-07-14: Sato Hub changed the scoring method (57 → 56). Not a change by the project.2026-09-01: Sato Hub changed the scoring method (56 → 74). Not a change by the project.2026-06-16: 33 (Low)2026-06-17: 54 (Medium)2026-06-18: 54 (Medium)2026-06-19: 54 (Medium)2026-06-20: 55 (Medium)2026-06-22: 55 (Medium)2026-06-24: 55 (Medium)2026-06-25: 69 (Medium)2026-06-26: 69 (Medium)2026-06-27: 69 (Medium)2026-06-30: 69 (Medium)2026-07-01: 69 (Medium)2026-07-02: 69 (Medium)2026-07-03: 69 (Medium)2026-07-04: 57 (Medium)2026-07-05: 57 (Medium)2026-07-06: 57 (Medium)2026-07-07: 57 (Medium)2026-07-08: 57 (Medium)2026-07-09: 57 (Medium)2026-07-10: 57 (Medium)2026-07-11: 57 (Medium)2026-07-12: 57 (Medium)2026-07-13: 57 (Medium)2026-07-14: 56 (Medium)2026-07-15: 56 (Medium)2026-07-16: 56 (Medium)2026-07-17: 56 (Medium)2026-07-18: 56 (Medium)2026-07-19: 56 (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: 74 (High)2026-09-02: 74 (High)2026-09-03: 74 (High)2026-09-04: 74 (High)2026-09-05: 74 (High)2026-09-06: 74 (High)2026-09-07: 74 (High)2026-09-08: 74 (High)2026-09-09: 74 (High)2026-09-10: 75 (High)2026-09-11: 75 (High)2026-09-12: 75 (High)2026-09-13: 75 (High)3375752026-06-162026-09-13

4 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

3 changes attributable to the project, 4 caused by a revision of the scoring method.

DateFromToChangeCause
2026-09-107475+1the project
2026-09-015674+18Sato Hub changed the scoring method
2026-07-145756-1Sato Hub changed the scoring method
2026-07-046957-12the project
2026-06-255569+14Sato Hub changed the scoring method
2026-06-205455+1the project
2026-06-173354+21Sato 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.

Maintenance & liveness35/35
35
Code transparency20/20
20
Interface verifiability0/10
10
Docs & demo4/10
10
Listing transparency & provenance13/15
15
Independent verification3/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-1375HighEarlyup
2026-09-1275HighEarlyup
2026-09-1175HighEarlyup
2026-09-1075HighEarlyup
2026-09-0974HighEarlyup
2026-09-0874HighEarlyup
2026-09-0774HighEarlyup
2026-09-0674HighEarlyup
2026-09-0574HighEarlyup
2026-09-0474HighEarlyup
2026-09-0374HighEarlyup
2026-09-0274HighEarlyup
2026-09-0174HighEarlyup
2026-08-3156MediumEarlyup
2026-08-3056MediumEarlyup
2026-08-2956MediumEarlyup
2026-08-2856MediumEarlyup
2026-08-2756MediumEarlyup
2026-08-2656MediumEarlyup
2026-08-2556MediumEarlyup
2026-08-2456MediumEarlyup
2026-08-2356MediumEarlyup
2026-08-2256MediumEarlyup
2026-08-2156MediumEarlyup
2026-08-2056MediumEarlyup
2026-08-1956MediumEarlyup
2026-08-1856MediumEarlyup
2026-08-1756MediumEarlyup
2026-08-1656MediumEarlyup
2026-08-1556MediumEarlyup
2026-08-1456MediumEarlyup
2026-08-1356MediumEarlyup
2026-08-1256MediumEarlyup
2026-08-1156MediumEarlyup
2026-08-1056MediumEarlyup
2026-08-0956MediumEarlyup
2026-08-0856MediumEarlyup
2026-08-0756MediumEarlyup
2026-08-0656MediumEarlyup
2026-08-0556MediumEarlyup
2026-08-0456MediumEarlyup
2026-08-0356MediumEarlyup
2026-08-0256MediumEarlyup
2026-08-0156MediumEarlyup
2026-07-3156MediumEarlyup
2026-07-3056MediumEarlyup
2026-07-2956MediumEarlyup
2026-07-2856MediumEarlyup
2026-07-2756MediumEarlyup
2026-07-2656MediumEarlyup
2026-07-2556MediumEarlyup
2026-07-2456MediumEarlyup
2026-07-2356MediumEarlyup
2026-07-2256MediumEarlyup
2026-07-2156MediumEarlyup
2026-07-2056MediumEarlyup
2026-07-1956MediumEarlyup
2026-07-1856MediumEarlyup
2026-07-1756MediumEarlyup
2026-07-1656MediumEarlyup
2026-07-1556MediumEarlyup
2026-07-1456MediumEarlyup
2026-07-1357MediumEarlynot checked
2026-07-1257MediumEarlynot checked
2026-07-1157MediumEarlynot checked
2026-07-1057MediumEarlynot checked
2026-07-0957MediumEarlynot checked
2026-07-0857MediumEarlynot checked
2026-07-0757MediumEarlynot checked
2026-07-0657MediumEarlynot checked
2026-07-0557MediumEarlynot checked
2026-07-0457MediumEarlynot checked
2026-07-0369MediumEarlynot checked
2026-07-0269MediumEarlynot checked
2026-07-0169MediumEarlynot checked
2026-06-3069MediumEarlynot checked
2026-06-2769MediumEarlynot checked
2026-06-2669MediumEarlynot checked
2026-06-2569MediumEarlynot checked
2026-06-2455MediumEarlynot checked
2026-06-2255MediumEarlynot checked
2026-06-2055MediumEarlynot checked
2026-06-1954MediumEarlynot checked
2026-06-1854MediumEarlynot checked
2026-06-1754MediumEarlynot checked
2026-06-1633LowEarlynot 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. Sep 12, 2026
    New release published
  2. Sep 10, 2026
    Crossed 1k GitHub stars
    147 → 1268.
  3. Sep 1, 2026
    Sato Score tier: Medium → High
    Score 56 → 74.
  4. Sep 1, 2026
    Active again — shipped after a quiet spell
  5. Aug 31, 2026
    New release published
  6. Jul 14, 2026
    Edited: deploy spec
  7. Jun 25, 2026
    Enriched: creator name, marketplace notes
  8. Jun 25, 2026
    Auto-enriched: creator profile url, website url, chains supported, tags +4 more
  9. Jun 17, 2026
    Sato Score tier: Low → Medium
    Score 33 → 54.
  10. Jun 16, 2026
    Sato Hub began tracking this listing
  11. Jun 16, 2026
    Edited: category, github url, description short

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.