Sato Hub
Solentic verification record

Score history

Solentic

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

50

Change over 57d

+8

Days measured

57

Days missed

0

Sato Score, daily

2026-07-192026-09-13
02550751002026-07-20: Sato Hub changed the scoring method (42 → 43). Not a change by the project.2026-09-01: Sato Hub changed the scoring method (53 → 55). Not a change by the project.2026-07-19: 42 (Medium)2026-07-20: 43 (Medium)2026-07-21: 43 (Medium)2026-07-22: 43 (Medium)2026-07-23: 43 (Medium)2026-07-24: 43 (Medium)2026-07-25: 43 (Medium)2026-07-26: 43 (Medium)2026-07-27: 53 (Medium)2026-07-28: 53 (Medium)2026-07-29: 53 (Medium)2026-07-30: 53 (Medium)2026-07-31: 53 (Medium)2026-08-01: 53 (Medium)2026-08-02: 53 (Medium)2026-08-03: 53 (Medium)2026-08-04: 53 (Medium)2026-08-05: 53 (Medium)2026-08-06: 53 (Medium)2026-08-07: 53 (Medium)2026-08-08: 53 (Medium)2026-08-09: 53 (Medium)2026-08-10: 53 (Medium)2026-08-11: 53 (Medium)2026-08-12: 53 (Medium)2026-08-13: 53 (Medium)2026-08-14: 53 (Medium)2026-08-15: 53 (Medium)2026-08-16: 53 (Medium)2026-08-17: 53 (Medium)2026-08-18: 53 (Medium)2026-08-19: 53 (Medium)2026-08-20: 53 (Medium)2026-08-21: 53 (Medium)2026-08-22: 53 (Medium)2026-08-23: 53 (Medium)2026-08-24: 53 (Medium)2026-08-25: 53 (Medium)2026-08-26: 53 (Medium)2026-08-27: 53 (Medium)2026-08-28: 53 (Medium)2026-08-29: 53 (Medium)2026-08-30: 53 (Medium)2026-08-31: 53 (Medium)2026-09-01: 55 (Medium)2026-09-02: 55 (Medium)2026-09-03: 55 (Medium)2026-09-04: 55 (Medium)2026-09-05: 55 (Medium)2026-09-06: 55 (Medium)2026-09-07: 55 (Medium)2026-09-08: 55 (Medium)2026-09-09: 55 (Medium)2026-09-10: 55 (Medium)2026-09-11: 55 (Medium)2026-09-12: 55 (Medium)2026-09-13: 50 (Medium)4255502026-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

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

DateFromToChangeCause
2026-09-135550-5the project
2026-09-015355+2Sato Hub changed the scoring method
2026-07-274353+10the project
2026-07-204243+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 transparency12/20
20
Interface verifiability0/10
10
Docs & demo6/10
10
Listing transparency & provenance10/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: failed, unattributable2026-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: failed on our side — not attributable to the project2026-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-1350MediumEarlyup
2026-09-1255MediumEarlyup
2026-09-1155MediumEarlyup
2026-09-1055MediumEarlyup
2026-09-0955MediumEarlyup
2026-09-0855MediumEarlyinconclusive
2026-09-0755MediumEarlyup
2026-09-0655MediumEarlyup
2026-09-0555MediumEarlyup
2026-09-0455MediumEarlyup
2026-09-0355MediumEarlyup
2026-09-0255MediumEarlyup
2026-09-0155MediumEarlyup
2026-08-3153MediumEarlyup
2026-08-3053MediumEarlyup
2026-08-2953MediumEarlyup
2026-08-2853MediumEarlyup
2026-08-2753MediumEarlyup
2026-08-2653MediumEarlyup
2026-08-2553MediumEarlyup
2026-08-2453MediumEarlyup
2026-08-2353MediumEarlyup
2026-08-2253MediumEarlyup
2026-08-2153MediumEarlyup
2026-08-2053MediumEarlyup
2026-08-1953MediumEarlyup
2026-08-1853MediumEarlyup
2026-08-1753MediumEarlyup
2026-08-1653MediumEarlyup
2026-08-1553MediumEarlyup
2026-08-1453MediumEarlyup
2026-08-1353MediumEarlyup
2026-08-1253MediumEarlyup
2026-08-1153MediumEarlyup
2026-08-1053MediumEarlyup
2026-08-0953MediumEarlyup
2026-08-0853MediumEarlyup
2026-08-0753MediumEarlyup
2026-08-0653MediumEarlyup
2026-08-0553MediumEarlyup
2026-08-0453MediumEarlyup
2026-08-0353MediumEarlyup
2026-08-0253MediumEarlyup
2026-08-0153MediumEarlyup
2026-07-3153MediumEarlyup
2026-07-3053MediumEarlyup
2026-07-2953MediumEarlyup
2026-07-2853MediumEarlyup
2026-07-2753MediumEarlyup
2026-07-2643MediumEarlyunknown
2026-07-2543MediumEarlyup
2026-07-2443MediumEarlyup
2026-07-2343MediumEarlyup
2026-07-2243MediumEarlyup
2026-07-2143MediumEarlyup
2026-07-2043MediumEarlyup
2026-07-1942MediumEarlyup

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. Jul 27, 2026
    Auto-enriched: docs url, deployment options
  2. Jul 20, 2026
    Edited: deploy spec
  3. Jul 19, 2026
    Edited: description short
  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.