Sato Hub
Score history

Circle Skills

One dated Sato Score reading per day. Days we changed the scoring method are marked. Not a safety or returns grade.

Score today

78

Change over 109d

+44

Days measured

109

Days missed

0

Sato Score, daily

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

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

DateFromToChangeCause
2026-10-196878+10the project
2026-09-137868-10the project
2026-09-017578+3Sato Hub changed the scoring method
2026-08-146575+10the project
2026-07-155665+9Sato Hub changed the scoring method
2026-07-143456+22Sato 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 transparency19/20
20
Interface verifiability0/10
10
Docs & demo6/10
10
Listing transparency & provenance15/15
15
Independent verification3/10
10

The observed record

100% of 108 daily checks since 2026-07-14 succeeded. This is the share of OUR checks that succeeded. It is not uptime: a failed check can be on our side. When a check before 2026-09-01 failed, the checks before that date are left out of the rate: the probe counted a bot-block as a failure then and recorded no reason for any failure.

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 check2026-09-14: answered our check2026-09-15: answered our check2026-09-16: answered our check2026-09-17: answered our check2026-09-18: answered our check2026-09-19: answered our check2026-09-20: answered our check2026-09-21: answered our check2026-09-22: answered our check2026-09-23: answered our check2026-09-24: answered our check2026-09-25: answered our check2026-09-26: answered our check2026-09-27: answered our check2026-09-28: answered our check2026-09-29: answered our check2026-09-30: answered our check2026-10-01: answered our check2026-10-02: answered our check2026-10-03: answered our check2026-10-04: answered our check2026-10-05: answered our check2026-10-06: answered our check2026-10-07: answered our check2026-10-08: answered our check2026-10-09: answered our check2026-10-10: answered our check2026-10-11: answered our check2026-10-12: answered our check2026-10-13: answered our check2026-10-14: answered our check2026-10-15: answered our check2026-10-16: answered our check2026-10-17: answered our check2026-10-18: answered our check2026-10-19: answered our check2026-10-20: answered our check2026-10-21: answered our check2026-10-22: answered our check2026-10-23: answered our check2026-10-24: answered our check2026-10-25: answered our check2026-10-26: answered our check2026-10-27: answered our check2026-10-28: answered our check2026-10-29: 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-10-2978HighActiveup
2026-10-2878HighActiveup
2026-10-2778HighActiveup
2026-10-2678HighActiveup
2026-10-2578HighActiveup
2026-10-2478HighActiveup
2026-10-2378HighActiveup
2026-10-2278HighActiveup
2026-10-2178HighActiveup
2026-10-2078HighActiveup
2026-10-1978HighActiveup
2026-10-1868MediumActiveup
2026-10-1768MediumActiveup
2026-10-1668MediumActiveup
2026-10-1568MediumActiveup
2026-10-1468MediumActiveup
2026-10-1368MediumActiveup
2026-10-1268MediumActiveup
2026-10-1168MediumActiveup
2026-10-1068MediumActiveup
2026-10-0968MediumActiveup
2026-10-0868MediumActiveup
2026-10-0768MediumActiveup
2026-10-0668MediumActiveup
2026-10-0568MediumActiveup
2026-10-0468MediumActiveup
2026-10-0368MediumActiveup
2026-10-0268MediumActiveup
2026-10-0168MediumActiveup
2026-09-3068MediumActiveup
2026-09-2968MediumActiveup
2026-09-2868MediumActiveup
2026-09-2768MediumActiveup
2026-09-2668MediumActiveup
2026-09-2568MediumActiveup
2026-09-2468MediumActiveup
2026-09-2368MediumActiveup
2026-09-2268MediumActiveup
2026-09-2168MediumActiveup
2026-09-2068MediumActiveup
2026-09-1968MediumActiveup
2026-09-1868MediumActiveup
2026-09-1768MediumActiveup
2026-09-1668MediumActiveup
2026-09-1568MediumActiveup
2026-09-1468MediumActiveup
2026-09-1368MediumActiveup
2026-09-1278HighActiveup
2026-09-1178HighActiveup
2026-09-1078HighActiveup
2026-09-0978HighActiveup
2026-09-0878HighActiveup
2026-09-0778HighActiveup
2026-09-0678HighActiveup
2026-09-0578HighActiveup
2026-09-0478HighActiveup
2026-09-0378HighActiveup
2026-09-0278HighActiveup
2026-09-0178HighActiveup
2026-08-3175HighActiveup
2026-08-3075HighActiveup
2026-08-2975HighActiveup
2026-08-2875HighActiveup
2026-08-2775HighActiveup
2026-08-2675HighActiveup
2026-08-2575HighActiveup
2026-08-2475HighActiveup
2026-08-2375HighActiveup
2026-08-2275HighActiveup
2026-08-2175HighActiveup
2026-08-2075HighActiveup
2026-08-1975HighActiveup
2026-08-1875HighActiveup
2026-08-1775HighActiveup
2026-08-1675HighActiveup
2026-08-1575HighActiveup
2026-08-1475HighActiveup
2026-08-1365MediumActiveup
2026-08-1265MediumActiveup
2026-08-1165MediumActiveup
2026-08-1065MediumActiveup
2026-08-0965MediumActiveup
2026-08-0865MediumActiveup
2026-08-0765MediumActiveup
2026-08-0665MediumActiveup
2026-08-0565MediumActiveup
2026-08-0465MediumActiveup
2026-08-0365MediumActiveup
2026-08-0265MediumActiveup
2026-08-0165MediumActiveup
2026-07-3165MediumActiveup
2026-07-3065MediumActiveup
2026-07-2965MediumActiveup
2026-07-2865MediumActiveup
2026-07-2765MediumActiveup
2026-07-2665MediumActiveup
2026-07-2565MediumActiveup
2026-07-2465MediumActiveup
2026-07-2365MediumActiveup
2026-07-2265MediumActiveup
2026-07-2165MediumActiveup
2026-07-2065MediumActiveup
2026-07-1965MediumActiveup
2026-07-1865MediumActiveup
2026-07-1765MediumActiveup
2026-07-1665MediumActiveup
2026-07-1565MediumActiveup
2026-07-1456MediumActiveup
2026-07-1334LowActivenot 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. Oct 19, 2026
    Sato Score tier: Medium → High
    Score 68 → 78.
  2. Sep 13, 2026
    Sato Score tier: High → Medium
    Score 78 → 68.
  3. Aug 14, 2026
    Sato Score tier: Medium → High
    Score 65 → 75.
  4. Aug 1, 2026
    Sato Hub began tracking this listing
  5. Jul 14, 2026
    Enriched: deployment options, supported integrations
  6. Jul 14, 2026
    Auto-enriched: x url, docs url
  7. Jul 13, 2026
    Listed on Sato Hub

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.