Sato Hub
QuickNode verification record

Score history

QuickNode

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

70

Change over 90d

+5

Days measured

90

Days missed

4

Sato Score, daily

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

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

DateFromToChangeCause
2026-09-037570-5the project
2026-09-017275+3Sato Hub changed the scoring method
2026-08-226872+4the project
2026-08-147268-4the project
2026-07-206672+6Sato Hub changed the scoring method
2026-07-146366+3Sato Hub changed the scoring method
2026-07-057363-10the project
2026-06-256573+8Sato 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 & liveness20/35
35
Code transparency12/20
20
Interface verifiability8/10
10
Docs & demo6/10
10
Listing transparency & provenance15/15
15
Independent verification9/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-1370HighActiveup
2026-09-1270HighActiveup
2026-09-1170HighActiveup
2026-09-1070HighActiveup
2026-09-0970HighActiveup
2026-09-0870HighActiveup
2026-09-0770HighActiveup
2026-09-0670HighActiveup
2026-09-0570HighActiveup
2026-09-0470HighActiveup
2026-09-0370HighActiveup
2026-09-0275HighActiveup
2026-09-0175HighActiveup
2026-08-3172HighActiveup
2026-08-3072HighActiveup
2026-08-2972HighActiveup
2026-08-2872HighActiveup
2026-08-2772HighActiveup
2026-08-2672HighActiveup
2026-08-2572HighActiveup
2026-08-2472HighActiveup
2026-08-2372HighActiveup
2026-08-2272HighActiveup
2026-08-2168MediumActiveup
2026-08-2068MediumActiveup
2026-08-1968MediumActiveup
2026-08-1868MediumActiveup
2026-08-1768MediumActiveup
2026-08-1668MediumActiveup
2026-08-1568MediumActiveup
2026-08-1468MediumActiveup
2026-08-1372HighActiveup
2026-08-1272HighActiveup
2026-08-1172HighActiveup
2026-08-1072HighActiveup
2026-08-0972HighActiveup
2026-08-0872HighActiveup
2026-08-0772HighActiveup
2026-08-0672HighActiveup
2026-08-0572HighActiveup
2026-08-0472HighActiveup
2026-08-0372HighActiveup
2026-08-0272HighActiveup
2026-08-0172HighActiveup
2026-07-3172HighActiveup
2026-07-3072HighActiveup
2026-07-2972HighActiveup
2026-07-2872HighActiveup
2026-07-2772HighActiveup
2026-07-2672HighActiveup
2026-07-2572HighActiveup
2026-07-2472HighActiveup
2026-07-2372HighActiveup
2026-07-2272HighActiveup
2026-07-2172HighActiveup
2026-07-2072HighActiveup
2026-07-1966MediumActiveup
2026-07-1866MediumActiveup
2026-07-1766MediumActiveup
2026-07-1666MediumActiveup
2026-07-1566MediumActiveup
2026-07-1466MediumActiveup
2026-07-1363MediumActivenot checked
2026-07-1263MediumActivenot checked
2026-07-1163MediumActivenot checked
2026-07-1063MediumActivenot checked
2026-07-0963MediumActivenot checked
2026-07-0863MediumActivenot checked
2026-07-0763MediumActivenot checked
2026-07-0663MediumActivenot checked
2026-07-0563MediumActivenot checked
2026-07-0473HighActivenot checked
2026-07-0373HighActivenot checked
2026-07-0273HighActivenot checked
2026-07-0173HighActivenot checked
2026-06-3073HighActivenot checked
2026-06-2773HighActivenot checked
2026-06-2673HighActivenot checked
2026-06-2573HighActivenot checked
2026-06-2465MediumActivenot checked
2026-06-2265MediumActivenot checked
2026-06-2065MediumActivenot checked
2026-06-1965MediumActivenot checked
2026-06-1865MediumActivenot checked
2026-06-1765MediumActivenot checked
2026-06-1665MediumActivenot checked
2026-06-1565MediumActivenot checked
2026-06-1465MediumActivenot checked
2026-06-1365MediumActivenot checked
2026-06-1265MediumActivenot checked
2026-06-11unknownActivenot 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. Aug 22, 2026
    Sato Score tier: Medium → High
    Score 68 → 72.
  2. Aug 14, 2026
    Sato Score tier: High → Medium
    Score 72 → 68.
  3. Jul 20, 2026
    Sato Score tier: Medium → High
    Score 66 → 72.
  4. Jul 14, 2026
    Edited: deploy spec
  5. Jul 5, 2026
    Sato Score tier: High → Medium
    Score 73 → 63.
  6. Jun 25, 2026
    Enriched: creator name, marketplace notes
  7. Jun 25, 2026
    Auto-enriched: supported integrations, deployment options, chains supported, has pricing
  8. Jun 25, 2026
    Sato Score tier: Medium → High
    Score 65 → 73.
  9. 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.