Sato Hub
← ChainAware verification record

Score history

ChainAware

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

67

Change over 90d

+3

Days measured

90

Days missed

4

Sato Score, daily

2026-06-11 → 2026-09-13
02550751002026-06-17: Sato Hub changed the scoring method (74 → 75). Not a change by the project.2026-06-25: Sato Hub changed the scoring method (74 → 82). Not a change by the project.2026-07-14: Sato Hub changed the scoring method (82 → 73). Not a change by the project.2026-09-01: Sato Hub changed the scoring method (74 → 77). Not a change by the project.2026-06-12: 64 (Medium)2026-06-13: 74 (High)2026-06-14: 74 (High)2026-06-15: 74 (High)2026-06-16: 74 (High)2026-06-17: 75 (High)2026-06-18: 74 (High)2026-06-19: 74 (High)2026-06-20: 74 (High)2026-06-22: 74 (High)2026-06-24: 74 (High)2026-06-25: 82 (High)2026-06-26: 82 (High)2026-06-27: 82 (High)2026-06-30: 82 (High)2026-07-01: 82 (High)2026-07-02: 82 (High)2026-07-03: 82 (High)2026-07-04: 82 (High)2026-07-05: 82 (High)2026-07-06: 82 (High)2026-07-07: 82 (High)2026-07-08: 82 (High)2026-07-09: 82 (High)2026-07-10: 82 (High)2026-07-11: 82 (High)2026-07-12: 82 (High)2026-07-13: 82 (High)2026-07-14: 73 (High)2026-07-15: 73 (High)2026-07-16: 73 (High)2026-07-17: 73 (High)2026-07-18: 73 (High)2026-07-19: 73 (High)2026-07-20: 73 (High)2026-07-21: 73 (High)2026-07-22: 73 (High)2026-07-23: 73 (High)2026-07-24: 73 (High)2026-07-25: 63 (Medium)2026-07-26: 63 (Medium)2026-07-27: 63 (Medium)2026-07-28: 63 (Medium)2026-07-29: 63 (Medium)2026-07-30: 63 (Medium)2026-07-31: 63 (Medium)2026-08-01: 63 (Medium)2026-08-02: 63 (Medium)2026-08-03: 63 (Medium)2026-08-04: 63 (Medium)2026-08-05: 63 (Medium)2026-08-06: 63 (Medium)2026-08-07: 63 (Medium)2026-08-08: 63 (Medium)2026-08-09: 63 (Medium)2026-08-10: 63 (Medium)2026-08-11: 63 (Medium)2026-08-12: 74 (High)2026-08-13: 74 (High)2026-08-14: 74 (High)2026-08-15: 74 (High)2026-08-16: 74 (High)2026-08-17: 74 (High)2026-08-18: 74 (High)2026-08-19: 74 (High)2026-08-20: 74 (High)2026-08-21: 74 (High)2026-08-22: 74 (High)2026-08-23: 74 (High)2026-08-24: 74 (High)2026-08-25: 74 (High)2026-08-26: 74 (High)2026-08-27: 74 (High)2026-08-28: 74 (High)2026-08-29: 74 (High)2026-08-30: 74 (High)2026-08-31: 74 (High)2026-09-01: 77 (High)2026-09-02: 77 (High)2026-09-03: 77 (High)2026-09-04: 77 (High)2026-09-05: 77 (High)2026-09-06: 77 (High)2026-09-07: 77 (High)2026-09-08: 77 (High)2026-09-09: 77 (High)2026-09-10: 77 (High)2026-09-11: 67 (Medium)2026-09-12: 67 (Medium)2026-09-13: 67 (Medium)6482672026-06-122026-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

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

DateFromToChangeCause
2026-09-117767-10the project
2026-09-017477+3Sato Hub changed the scoring method
2026-08-126374+11the project
2026-07-257363-10the project
2026-07-148273-9Sato Hub changed the scoring method
2026-06-257482+8Sato Hub changed the scoring method
2026-06-187574-1the project
2026-06-177475+1Sato Hub changed the scoring method
2026-06-136474+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 & liveness25/35
35
Code transparency14/20
20
Interface verifiability0/10
10
Docs & demo10/10
10
Listing transparency & provenance15/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-1367MediumActiveup
2026-09-1267MediumActiveup
2026-09-1167MediumActiveup
2026-09-1077HighActiveup
2026-09-0977HighActiveup
2026-09-0877HighActiveup
2026-09-0777HighActiveup
2026-09-0677HighActiveup
2026-09-0577HighActiveup
2026-09-0477HighActiveup
2026-09-0377HighActiveup
2026-09-0277HighActiveup
2026-09-0177HighActiveup
2026-08-3174HighActiveup
2026-08-3074HighActiveup
2026-08-2974HighActiveup
2026-08-2874HighActiveup
2026-08-2774HighActiveup
2026-08-2674HighActiveup
2026-08-2574HighActiveup
2026-08-2474HighActiveup
2026-08-2374HighActiveup
2026-08-2274HighActiveup
2026-08-2174HighActiveup
2026-08-2074HighActiveup
2026-08-1974HighActiveup
2026-08-1874HighActiveup
2026-08-1774HighActiveup
2026-08-1674HighActiveup
2026-08-1574HighActiveup
2026-08-1474HighActiveup
2026-08-1374HighActiveup
2026-08-1274HighActiveup
2026-08-1163MediumActiveup
2026-08-1063MediumActiveup
2026-08-0963MediumActiveup
2026-08-0863MediumActiveup
2026-08-0763MediumActiveup
2026-08-0663MediumActiveup
2026-08-0563MediumActiveup
2026-08-0463MediumActiveup
2026-08-0363MediumActiveup
2026-08-0263MediumActiveup
2026-08-0163MediumActiveup
2026-07-3163MediumActiveup
2026-07-3063MediumActiveup
2026-07-2963MediumActiveup
2026-07-2863MediumActiveup
2026-07-2763MediumActiveup
2026-07-2663MediumActiveup
2026-07-2563MediumActiveup
2026-07-2473HighActiveup
2026-07-2373HighActiveup
2026-07-2273HighActiveup
2026-07-2173HighActiveup
2026-07-2073HighActiveup
2026-07-1973HighActiveup
2026-07-1873HighActiveup
2026-07-1773HighActiveup
2026-07-1673HighActiveup
2026-07-1573HighActiveup
2026-07-1473HighActiveup
2026-07-1382HighActivenot checked
2026-07-1282HighActivenot checked
2026-07-1182HighActivenot checked
2026-07-1082HighActivenot checked
2026-07-0982HighActivenot checked
2026-07-0882HighActivenot checked
2026-07-0782HighActivenot checked
2026-07-0682HighActivenot checked
2026-07-0582HighActivenot checked
2026-07-0482HighActivenot checked
2026-07-0382HighActivenot checked
2026-07-0282HighActivenot checked
2026-07-0182HighActivenot checked
2026-06-3082HighActivenot checked
2026-06-2782HighActivenot checked
2026-06-2682HighActivenot checked
2026-06-2582HighActivenot checked
2026-06-2474HighActivenot checked
2026-06-2274HighActivenot checked
2026-06-2074HighActivenot checked
2026-06-1974HighActivenot checked
2026-06-1874HighActivenot checked
2026-06-1775HighActivenot checked
2026-06-1674HighActivenot checked
2026-06-1574HighActivenot checked
2026-06-1474HighActivenot checked
2026-06-1374HighActivenot checked
2026-06-1264MediumActivenot checked
2026-06-11unknown—Activenot 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 11, 2026
    Sato Score tier: High → Medium
    Score 77 → 67.
  2. Aug 12, 2026
    Sato Score tier: Medium → High
    Score 63 → 74.
  3. Jul 25, 2026
    Sato Score tier: High → Medium
    Score 73 → 63.
  4. Jul 14, 2026
    Edited: deploy spec
  5. Jun 25, 2026
    Enriched: deployment options, supported integrations, has pricing, marketplace notes
  6. Jun 25, 2026
    Auto-enriched: creator name, creator profile url, chains supported
  7. Jun 13, 2026
    Sato Score tier: Medium → High
    Score 64 → 74.
  8. Jun 12, 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