Sato Hub
← Flaunch verification record

Score history

Flaunch

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

77

Change over 57d

+29

Days measured

57

Days missed

0

Sato Score, daily

2026-07-19 → 2026-09-13
02550751002026-07-20: Sato Hub changed the scoring method (48 → 57). Not a change by the project.2026-09-01: Sato Hub changed the scoring method (74 → 77). Not a change by the project.2026-07-19: 48 (Medium)2026-07-20: 57 (Medium)2026-07-21: 59 (Medium)2026-07-22: 59 (Medium)2026-07-23: 74 (High)2026-07-24: 74 (High)2026-07-25: 74 (High)2026-07-26: 74 (High)2026-07-27: 74 (High)2026-07-28: 74 (High)2026-07-29: 74 (High)2026-07-30: 74 (High)2026-07-31: 74 (High)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: 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: 64 (Medium)2026-08-24: 64 (Medium)2026-08-25: 64 (Medium)2026-08-26: 64 (Medium)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: 77 (High)2026-09-12: 77 (High)2026-09-13: 77 (High)4877772026-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

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

DateFromToChangeCause
2026-09-017477+3Sato Hub changed the scoring method
2026-08-276474+10the project
2026-08-237464-10the project
2026-07-235974+15the project
2026-07-215759+2the project
2026-07-204857+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 & liveness35/35
35
Code transparency18/20
20
Interface verifiability8/10
10
Docs & demo6/10
10
Listing transparency & provenance7/15
15
Independent verification3/10
10

The observed record

100% 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: 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-1377HighActiveup
2026-09-1277HighActiveup
2026-09-1177HighActiveup
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-2664MediumActiveup
2026-08-2564MediumActiveup
2026-08-2464MediumActiveup
2026-08-2364MediumActiveup
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-1174HighActiveup
2026-08-1074HighActiveup
2026-08-0974HighActiveup
2026-08-0874HighActiveup
2026-08-0774HighActiveup
2026-08-0674HighActiveup
2026-08-0574HighActiveup
2026-08-0474HighActiveup
2026-08-0374HighActiveup
2026-08-0274HighActiveup
2026-08-0174HighActiveup
2026-07-3174HighActiveup
2026-07-3074HighActiveup
2026-07-2974HighActiveup
2026-07-2874HighActiveup
2026-07-2774HighActiveup
2026-07-2674HighActiveup
2026-07-2574HighActiveup
2026-07-2474HighActiveup
2026-07-2374HighActiveup
2026-07-2259MediumActiveup
2026-07-2159MediumActiveup
2026-07-2057MediumActiveup
2026-07-1948MediumActiveup

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 8, 2026
    New release published
  2. Sep 4, 2026
    New release published
  3. Aug 27, 2026
    Sato Score tier: Medium → High
    Score 64 → 74.
  4. Aug 23, 2026
    Sato Score tier: High → Medium
    Score 74 → 64.
  5. Jul 23, 2026
    Sato Score tier: Medium → High
    Score 59 → 74.
  6. Jul 23, 2026
    Active again — shipped after a quiet spell
  7. Jul 23, 2026
    5 releases tracked
    Showing the 2 most recent. Full release history is retained in the listing record.
  8. Jul 21, 2026
    Verified: deploy spec
  9. Jul 19, 2026
    Edited: description long
  10. Jul 19, 2026
    Listed on Sato Hub
  11. 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