Sato Hub
← Enso verification record

Score history

Enso

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

+4

Days measured

90

Days missed

4

Sato Score, daily

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

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

DateFromToChangeCause
2026-09-016770+3Sato Hub changed the scoring method
2026-08-147767-10the project
2026-07-156777+10Sato Hub changed the scoring method
2026-07-146567+2Sato Hub changed the scoring method
2026-06-255765+8Sato Hub changed the scoring method
2026-06-196757-10the project
2026-06-176667+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 & liveness25/35
35
Code transparency13/20
20
Interface verifiability8/10
10
Docs & demo6/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-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-0270HighActiveup
2026-09-0170HighActiveup
2026-08-3167MediumActiveup
2026-08-3067MediumActiveup
2026-08-2967MediumActiveup
2026-08-2867MediumActiveup
2026-08-2767MediumActiveup
2026-08-2667MediumActiveup
2026-08-2567MediumActiveup
2026-08-2467MediumActiveup
2026-08-2367MediumActiveup
2026-08-2267MediumActiveup
2026-08-2167MediumActiveup
2026-08-2067MediumActiveup
2026-08-1967MediumActiveup
2026-08-1867MediumActiveup
2026-08-1767MediumActiveup
2026-08-1667MediumActiveup
2026-08-1567MediumActiveup
2026-08-1467MediumActiveup
2026-08-1377HighActiveup
2026-08-1277HighActiveup
2026-08-1177HighActiveup
2026-08-1077HighActiveup
2026-08-0977HighActiveup
2026-08-0877HighActiveup
2026-08-0777HighActiveup
2026-08-0677HighActiveup
2026-08-0577HighActiveup
2026-08-0477HighActiveup
2026-08-0377HighActiveup
2026-08-0277HighActiveup
2026-08-0177HighActiveup
2026-07-3177HighActiveup
2026-07-3077HighActiveup
2026-07-2977HighActiveup
2026-07-2877HighActiveup
2026-07-2777HighActiveup
2026-07-2677HighActiveup
2026-07-2577HighActiveup
2026-07-2477HighActiveup
2026-07-2377HighActiveup
2026-07-2277HighActiveup
2026-07-2177HighActiveup
2026-07-2077HighActiveup
2026-07-1977HighActiveup
2026-07-1877HighActiveup
2026-07-1777HighActiveup
2026-07-1677HighActiveup
2026-07-1577HighActiveup
2026-07-1467MediumActiveup
2026-07-1365MediumActivenot checked
2026-07-1265MediumActivenot checked
2026-07-1165MediumActivenot checked
2026-07-1065MediumActivenot checked
2026-07-0965MediumActivenot checked
2026-07-0865MediumActivenot checked
2026-07-0765MediumActivenot checked
2026-07-0665MediumActivenot checked
2026-07-0565MediumActivenot checked
2026-07-0465MediumActivenot checked
2026-07-0365MediumActivenot checked
2026-07-0265MediumActivenot checked
2026-07-0165MediumActivenot checked
2026-06-3065MediumActivenot checked
2026-06-2765MediumActivenot checked
2026-06-2665MediumActivenot checked
2026-06-2565MediumActivenot checked
2026-06-2457MediumActivenot checked
2026-06-2257MediumActivenot checked
2026-06-2057MediumActivenot checked
2026-06-1957MediumActivenot checked
2026-06-1867MediumActivenot checked
2026-06-1767MediumActivenot checked
2026-06-1666MediumActivenot checked
2026-06-1566MediumActivenot checked
2026-06-1466MediumActivenot checked
2026-06-1366MediumActivenot checked
2026-06-1266MediumActivenot 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 7, 2026
    Verified: deploy spec
  2. Sep 1, 2026
    Sato Score tier: Medium → High
    Score 67 → 70.
  3. Aug 14, 2026
    Sato Score tier: High → Medium
    Score 77 → 67.
  4. Jul 15, 2026
    Sato Score tier: Medium → High
    Score 67 → 77.
  5. Jul 14, 2026
    New release published
  6. Jun 25, 2026
    Auto-enriched: creator name, x url, supported integrations, deployment options +1 more
  7. 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