Sato Hub
Score history

Kraken CLI

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

Score today

74

Change over 109d

+10

Days measured

109

Days missed

0

Sato Score, daily

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

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

DateFromToChangeCause
2026-10-196474+10the project
2026-09-196564-1the project
2026-09-077565-10the project
2026-09-017275+3Sato Hub changed the scoring method
2026-08-085772+15the project
2026-07-196257-5the project
2026-07-156162+1Sato Hub changed the scoring method
2026-07-146461-3Sato 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 & provenance12/15
15
Independent verification2/10
10

The observed record

98.1% 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: failed on our side — not attributable to the project2026-09-19: answered our check2026-09-20: answered our check2026-09-21: failed on our side — not attributable to the project2026-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-2974HighActiveup
2026-10-2874HighActiveup
2026-10-2774HighActiveup
2026-10-2674HighActiveup
2026-10-2574HighActiveup
2026-10-2474HighActiveup
2026-10-2374HighActiveup
2026-10-2274HighActiveup
2026-10-2174HighActiveup
2026-10-2074HighActiveup
2026-10-1974HighActiveup
2026-10-1864MediumActiveup
2026-10-1764MediumActiveup
2026-10-1664MediumActiveup
2026-10-1564MediumActiveup
2026-10-1464MediumActiveup
2026-10-1364MediumActiveup
2026-10-1264MediumActiveup
2026-10-1164MediumActiveup
2026-10-1064MediumActiveup
2026-10-0964MediumActiveup
2026-10-0864MediumActiveup
2026-10-0764MediumActiveup
2026-10-0664MediumActiveup
2026-10-0564MediumActiveup
2026-10-0464MediumActiveup
2026-10-0364MediumActiveup
2026-10-0264MediumActiveup
2026-10-0164MediumActiveup
2026-09-3064MediumActiveup
2026-09-2964MediumActiveup
2026-09-2864MediumActiveup
2026-09-2764MediumActiveup
2026-09-2664MediumActiveup
2026-09-2564MediumActiveup
2026-09-2464MediumActiveup
2026-09-2364MediumActiveup
2026-09-2264MediumActiveup
2026-09-2164MediumActiveinconclusive
2026-09-2064MediumActiveup
2026-09-1964MediumActiveup
2026-09-1865MediumActiveinconclusive
2026-09-1765MediumActiveup
2026-09-1665MediumActiveup
2026-09-1565MediumActiveup
2026-09-1465MediumActiveup
2026-09-1365MediumActiveup
2026-09-1265MediumActiveup
2026-09-1165MediumActiveup
2026-09-1065MediumActiveup
2026-09-0965MediumActiveup
2026-09-0865MediumActiveup
2026-09-0765MediumActiveup
2026-09-0675HighActiveup
2026-09-0575HighActiveup
2026-09-0475HighActiveup
2026-09-0375HighActiveup
2026-09-0275HighActiveup
2026-09-0175HighActiveup
2026-08-3172HighActiveup
2026-08-3072HighActiveup
2026-08-2972HighActiveup
2026-08-2872HighActiveup
2026-08-2772HighActiveup
2026-08-2672HighActiveup
2026-08-2572HighActiveup
2026-08-2472HighActiveup
2026-08-2372HighActiveup
2026-08-2272HighActiveup
2026-08-2172HighActiveup
2026-08-2072HighActiveup
2026-08-1972HighActiveup
2026-08-1872HighActiveup
2026-08-1772HighActiveup
2026-08-1672HighActiveup
2026-08-1572HighActiveup
2026-08-1472HighActiveup
2026-08-1372HighActiveup
2026-08-1272HighActiveup
2026-08-1172HighActiveup
2026-08-1072HighActiveup
2026-08-0972HighActiveup
2026-08-0872HighActiveup
2026-08-0757MediumActiveup
2026-08-0657MediumActiveup
2026-08-0557MediumActiveup
2026-08-0457MediumActiveup
2026-08-0357MediumActiveup
2026-08-0257MediumActiveup
2026-08-0157MediumActiveup
2026-07-3157MediumActiveup
2026-07-3057MediumActiveup
2026-07-2957MediumActiveup
2026-07-2857MediumActiveup
2026-07-2757MediumActiveup
2026-07-2657MediumActiveup
2026-07-2557MediumActiveup
2026-07-2457MediumActiveup
2026-07-2357MediumActiveup
2026-07-2257MediumActiveup
2026-07-2157MediumActiveup
2026-07-2057MediumActiveup
2026-07-1957MediumActiveup
2026-07-1862MediumActiveup
2026-07-1762MediumActiveup
2026-07-1662MediumActiveup
2026-07-1562MediumActiveup
2026-07-1461MediumActiveup
2026-07-1364MediumActivenot 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 28, 2026
    New release published
  2. Oct 19, 2026
    Sato Score tier: Medium → High
    Score 64 → 74.
  3. Sep 7, 2026
    Sato Score tier: High → Medium
    Score 75 → 65.
  4. Aug 9, 2026
    Crossed 500 GitHub stars
    487 → 680.
  5. Aug 8, 2026
    Sato Score tier: Medium → High
    Score 57 → 72.
  6. Aug 8, 2026
    Active again — shipped after a quiet spell
  7. Aug 7, 2026
    New release published
  8. Aug 1, 2026
    Sato Hub began tracking this listing
  9. Jul 14, 2026
    Auto-enriched: deployment options, supported integrations
  10. 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.