Sato Hub
← NFTGo verification record

Score history

NFTGo

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

47

Change over 57d

+24

Days measured

57

Days missed

0

Sato Score, daily

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

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, 2 caused by a revision of the scoring method.

DateFromToChangeCause
2026-09-013247+15Sato Hub changed the scoring method
2026-07-262432+8the project
2026-07-202324+1Sato 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 transparency13/20
20
Interface verifiability0/10
10
Docs & demo6/10
10
Listing transparency & provenance8/15
15
Independent verification0/10
10

The observed record

22.8% of Sato Hub's own daily checks succeeded over 57 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-19: failed, unattributable2026-07-20: failed, unattributable2026-07-21: failed, unattributable2026-07-22: failed, unattributable2026-07-23: failed, unattributable2026-07-24: failed, unattributable2026-07-25: failed, unattributable2026-07-26: failed, unattributable2026-07-27: failed, unattributable2026-07-28: failed, unattributable2026-07-29: failed, unattributable2026-07-30: failed, unattributable2026-07-31: failed, unattributable2026-08-01: failed, unattributable2026-08-02: failed, unattributable2026-08-03: failed, unattributable2026-08-04: failed, unattributable2026-08-05: failed, unattributable2026-08-06: failed, unattributable2026-08-07: failed, unattributable2026-08-08: failed, unattributable2026-08-09: failed, unattributable2026-08-10: failed, unattributable2026-08-11: failed, unattributable2026-08-12: failed, unattributable2026-08-13: failed, unattributable2026-08-14: failed, unattributable2026-08-15: failed, unattributable2026-08-16: failed, unattributable2026-08-17: failed, unattributable2026-08-18: failed, unattributable2026-08-19: failed, unattributable2026-08-20: failed, unattributable2026-08-21: failed, unattributable2026-08-22: failed, unattributable2026-08-23: failed, unattributable2026-08-24: failed, unattributable2026-08-25: failed, unattributable2026-08-26: failed, unattributable2026-08-27: failed, unattributable2026-08-28: failed, unattributable2026-08-29: failed, unattributable2026-08-30: failed, unattributable2026-08-31: failed, unattributable2026-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-1347MediumEarlyup
2026-09-1247MediumEarlyup
2026-09-1147MediumEarlyup
2026-09-1047MediumEarlyup
2026-09-0947MediumEarlyup
2026-09-0847MediumEarlyup
2026-09-0747MediumEarlyup
2026-09-0647MediumEarlyup
2026-09-0547MediumEarlyup
2026-09-0447MediumEarlyup
2026-09-0347MediumEarlyup
2026-09-0247MediumEarlyup
2026-09-0147MediumEarlyup
2026-08-3132LowEarlyunknown
2026-08-3032LowEarlyunknown
2026-08-2932LowEarlyunknown
2026-08-2832LowEarlyunknown
2026-08-2732LowEarlyunknown
2026-08-2632LowEarlyunknown
2026-08-2532LowEarlyunknown
2026-08-2432LowEarlyunknown
2026-08-2332LowEarlyunknown
2026-08-2232LowEarlyunknown
2026-08-2132LowEarlyunknown
2026-08-2032LowEarlyunknown
2026-08-1932LowEarlyunknown
2026-08-1832LowEarlyunknown
2026-08-1732LowEarlyunknown
2026-08-1632LowEarlyunknown
2026-08-1532LowEarlyunknown
2026-08-1432LowEarlyunknown
2026-08-1332LowEarlyunknown
2026-08-1232LowEarlyunknown
2026-08-1132LowEarlyunknown
2026-08-1032LowEarlyunknown
2026-08-0932LowEarlyunknown
2026-08-0832LowEarlyunknown
2026-08-0732LowEarlyunknown
2026-08-0632LowEarlyunknown
2026-08-0532LowEarlyunknown
2026-08-0432LowEarlyunknown
2026-08-0332LowEarlyunknown
2026-08-0232LowEarlyunknown
2026-08-0132LowEarlyunknown
2026-07-3132LowEarlyunknown
2026-07-3032LowEarlyunknown
2026-07-2932LowEarlyunknown
2026-07-2832LowEarlyunknown
2026-07-2732LowEarlyunknown
2026-07-2632LowEarlyunknown
2026-07-2524LowEarlyunknown
2026-07-2424LowEarlyunknown
2026-07-2324LowEarlyunknown
2026-07-2224LowEarlyunknown
2026-07-2124LowEarlyunknown
2026-07-2024LowEarlyunknown
2026-07-1923LowEarlyunknown

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 1, 2026
    Sato Score tier: Low → Medium
    Score 32 → 47.
  2. Jul 26, 2026
    Auto-enriched: docs url
  3. Jul 20, 2026
    Edited: deploy spec
  4. Jul 19, 2026
    Listed on Sato Hub
  5. Jul 19, 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