Sato Hub
Score history

PulseFeed

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

Score today

84

Change over 47d

+1

Days measured

47

Days missed

0

Sato Score, daily

2026-10-04 → 2026-11-19
02550751002026-10-04: 83 (High)2026-10-05: 83 (High)2026-10-06: 83 (High)2026-10-07: 83 (High)2026-10-08: 83 (High)2026-10-09: 83 (High)2026-10-10: 83 (High)2026-10-11: 83 (High)2026-10-12: 83 (High)2026-10-13: 83 (High)2026-10-14: 83 (High)2026-10-15: 83 (High)2026-10-16: 83 (High)2026-10-17: 84 (High)2026-10-18: 84 (High)2026-10-19: 84 (High)2026-10-20: 84 (High)2026-10-21: 84 (High)2026-10-22: 84 (High)2026-10-23: 84 (High)2026-10-24: 84 (High)2026-10-25: 84 (High)2026-10-26: 84 (High)2026-10-27: 84 (High)2026-10-28: 84 (High)2026-10-29: 84 (High)2026-10-30: 84 (High)2026-10-31: 84 (High)2026-11-01: 86 (High)2026-11-02: 86 (High)2026-11-03: 86 (High)2026-11-04: 86 (High)2026-11-05: 86 (High)2026-11-06: 86 (High)2026-11-07: 86 (High)2026-11-08: 86 (High)2026-11-09: 86 (High)2026-11-10: 86 (High)2026-11-11: 86 (High)2026-11-12: 86 (High)2026-11-13: 86 (High)2026-11-14: 86 (High)2026-11-15: 86 (High)2026-11-16: 86 (High)2026-11-17: 86 (High)2026-11-18: 86 (High)2026-11-19: 84 (High)8386842026-10-042026-11-19

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

DateFromToChangeCause
2026-11-198684-2the project
2026-11-018486+2the project
2026-10-178384+1the project

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 transparency16/20
20
Interface verifiability10/10
10
Docs & demo6/10
10
Listing transparency & provenance10/15
15
Independent verification7/10
10

The observed record

97.9% of 47 daily checks since 2026-10-04 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-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 check2026-10-30: answered our check2026-10-31: answered our check2026-11-01: answered our check2026-11-02: answered our check2026-11-03: answered our check2026-11-04: answered our check2026-11-05: answered our check2026-11-06: answered our check2026-11-07: answered our check2026-11-08: answered our check2026-11-09: answered our check2026-11-10: answered our check2026-11-11: answered our check2026-11-12: answered our check2026-11-13: answered our check2026-11-14: answered our check2026-11-15: answered our check2026-11-16: answered our check2026-11-17: answered our check2026-11-18: answered our check2026-11-19: the host answered with an error
  • 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-11-1984HighEarlydown
2026-11-1886HighEarlyup
2026-11-1786HighEarlyup
2026-11-1686HighEarlyup
2026-11-1586HighEarlyup
2026-11-1486HighEarlyup
2026-11-1386HighEarlyup
2026-11-1286HighEarlyup
2026-11-1186HighEarlyup
2026-11-1086HighEarlyup
2026-11-0986HighEarlyup
2026-11-0886HighEarlyup
2026-11-0786HighEarlyup
2026-11-0686HighEarlyup
2026-11-0586HighEarlyup
2026-11-0486HighEarlyup
2026-11-0386HighEarlyup
2026-11-0286HighEarlyup
2026-11-0186HighEarlyup
2026-10-3184HighEarlyup
2026-10-3084HighEarlyup
2026-10-2984HighEarlyup
2026-10-2884HighEarlyup
2026-10-2784HighEarlyup
2026-10-2684HighEarlyup
2026-10-2584HighEarlyup
2026-10-2484HighEarlyup
2026-10-2384HighEarlyup
2026-10-2284HighEarlyup
2026-10-2184HighEarlyup
2026-10-2084HighEarlyup
2026-10-1984HighEarlyup
2026-10-1884HighEarlyup
2026-10-1784HighEarlyup
2026-10-1683HighEarlyup
2026-10-1583HighEarlyup
2026-10-1483HighEarlyup
2026-10-1383HighEarlyup
2026-10-1283HighEarlyup
2026-10-1183HighEarlyup
2026-10-1083HighEarlyup
2026-10-0983HighEarlyup
2026-10-0883HighEarlyup
2026-10-0783HighEarlyup
2026-10-0683HighEarlyup
2026-10-0583HighEarlyup
2026-10-0483HighEarlyup

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 4, 2026
    Auto-enriched: tags, supported integrations, deployment options, has pricing
  2. Oct 4, 2026
    Sato Hub began tracking this listing
  3. Oct 3, 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.