Sato Hub
← Printr verification record

Score history

Printr

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

66

Change over 57d

+9

Days measured

57

Days missed

0

Sato Score, daily

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

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

DateFromToChangeCause
2026-09-136766-1the project
2026-09-016467+3Sato Hub changed the scoring method
2026-08-177464-10the project
2026-08-016674+8the project
2026-07-205766+9Sato 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 & liveness25/35
35
Code transparency17/20
20
Interface verifiability8/10
10
Docs & demo6/10
10
Listing transparency & provenance8/15
15
Independent verification2/10
10

The observed record

96.5% 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: 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: failed on our side — not attributable to the project2026-09-13: failed on our side — not attributable to the project
  • 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-1366MediumEarlyinconclusive
2026-09-1267MediumEarlyinconclusive
2026-09-1167MediumEarlyup
2026-09-1067MediumEarlyup
2026-09-0967MediumEarlyup
2026-09-0867MediumEarlyup
2026-09-0767MediumEarlyup
2026-09-0667MediumEarlyup
2026-09-0567MediumEarlyup
2026-09-0467MediumEarlyup
2026-09-0367MediumEarlyup
2026-09-0267MediumEarlyup
2026-09-0167MediumEarlyup
2026-08-3164MediumEarlyup
2026-08-3064MediumEarlyup
2026-08-2964MediumEarlyup
2026-08-2864MediumEarlyup
2026-08-2764MediumEarlyup
2026-08-2664MediumEarlyup
2026-08-2564MediumEarlyup
2026-08-2464MediumEarlyup
2026-08-2364MediumEarlyup
2026-08-2264MediumEarlyup
2026-08-2164MediumEarlyup
2026-08-2064MediumEarlyup
2026-08-1964MediumEarlyup
2026-08-1864MediumEarlyup
2026-08-1764MediumEarlyup
2026-08-1674HighEarlyup
2026-08-1574HighEarlyup
2026-08-1474HighEarlyup
2026-08-1374HighEarlyup
2026-08-1274HighEarlyup
2026-08-1174HighEarlyup
2026-08-1074HighEarlyup
2026-08-0974HighEarlyup
2026-08-0874HighEarlyup
2026-08-0774HighEarlyup
2026-08-0674HighEarlyup
2026-08-0574HighEarlyup
2026-08-0474HighEarlyup
2026-08-0374HighEarlyup
2026-08-0274HighEarlyup
2026-08-0174HighEarlyup
2026-07-3166MediumEarlyup
2026-07-3066MediumEarlyup
2026-07-2966MediumEarlyup
2026-07-2866MediumEarlyup
2026-07-2766MediumEarlyup
2026-07-2666MediumEarlyup
2026-07-2566MediumEarlyup
2026-07-2466MediumEarlyup
2026-07-2366MediumEarlyup
2026-07-2266MediumEarlyup
2026-07-2166MediumEarlyup
2026-07-2066MediumEarlyup
2026-07-1957MediumEarlyup

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 17, 2026
    Sato Score tier: High → Medium
    Score 74 → 64.
  2. Aug 1, 2026
    Auto-enriched: docs url
  3. Aug 1, 2026
    Sato Score tier: Medium → High
    Score 66 → 74.
  4. Jul 21, 2026
    Verified: deploy spec
  5. Jul 19, 2026
    Listed on Sato Hub
  6. 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