Sato Hub
Score history

Bitrefill

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

Score today

32

Change over 103d

+20

Days measured

103

Days missed

0

Sato Score, daily

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

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

DateFromToChangeCause
2026-10-102932+3Sato Hub changed the scoring method
2026-09-011729+12Sato Hub changed the scoring method
2026-07-201217+5Sato 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 transparency0/20
20
Interface verifiability0/10
10
Docs & demo0/10
10
Listing transparency & provenance5/15
15
Independent verification7/10
10

The observed record

100% of 59 daily checks since 2026-09-01 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-19: failed, unattributable2026-07-20: failed, unattributable2026-07-21: failed, unattributable2026-07-22: failed, unattributable2026-07-23: failed, unattributable2026-07-24: failed, unattributable2026-07-25: failed, unattributable2026-07-26: failed, unattributable2026-07-27: failed, unattributable2026-07-28: failed, unattributable2026-07-29: failed, unattributable2026-07-30: failed, unattributable2026-07-31: failed, unattributable2026-08-01: failed, unattributable2026-08-02: failed, unattributable2026-08-03: failed, unattributable2026-08-04: failed, unattributable2026-08-05: failed, unattributable2026-08-06: failed, unattributable2026-08-07: failed, unattributable2026-08-08: failed, unattributable2026-08-09: failed, unattributable2026-08-10: failed, unattributable2026-08-11: failed, unattributable2026-08-12: failed, unattributable2026-08-13: failed, unattributable2026-08-14: failed, unattributable2026-08-15: failed, unattributable2026-08-16: failed, unattributable2026-08-17: failed, unattributable2026-08-18: failed, unattributable2026-08-19: failed, unattributable2026-08-20: failed, unattributable2026-08-21: failed, unattributable2026-08-22: failed, unattributable2026-08-23: failed, unattributable2026-08-24: failed, unattributable2026-08-25: failed, unattributable2026-08-26: failed, unattributable2026-08-27: failed, unattributable2026-08-28: failed, unattributable2026-08-29: failed, unattributable2026-08-30: failed, unattributable2026-08-31: failed, unattributable2026-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-2932LowActiveup
2026-10-2832LowActiveup
2026-10-2732LowActiveup
2026-10-2632LowActiveup
2026-10-2532LowActiveup
2026-10-2432LowActiveup
2026-10-2332LowActiveup
2026-10-2232LowActiveup
2026-10-2132LowActiveup
2026-10-2032LowActiveup
2026-10-1932LowActiveup
2026-10-1832LowActiveup
2026-10-1732LowActiveup
2026-10-1632LowActiveup
2026-10-1532LowActiveup
2026-10-1432LowActiveup
2026-10-1332LowActiveup
2026-10-1232LowActiveup
2026-10-1132LowActiveup
2026-10-1032LowActiveup
2026-10-0929LowActiveup
2026-10-0829LowActiveup
2026-10-0729LowActiveup
2026-10-0629LowActiveup
2026-10-0529LowActiveup
2026-10-0429LowActiveup
2026-10-0329LowActiveup
2026-10-0229LowActiveup
2026-10-0129LowActiveup
2026-09-3029LowActiveup
2026-09-2929LowActiveup
2026-09-2829LowActiveup
2026-09-2729LowActiveup
2026-09-2629LowActiveup
2026-09-2529LowActiveup
2026-09-2429LowActiveup
2026-09-2329LowActiveup
2026-09-2229LowActiveup
2026-09-2129LowActiveup
2026-09-2029LowActiveup
2026-09-1929LowActiveup
2026-09-1829LowActiveup
2026-09-1729LowActiveup
2026-09-1629LowActiveup
2026-09-1529LowActiveup
2026-09-1429LowActiveup
2026-09-1329LowActiveup
2026-09-1229LowActiveup
2026-09-1129LowActiveup
2026-09-1029LowActiveup
2026-09-0929LowActiveup
2026-09-0829LowActiveup
2026-09-0729LowActiveup
2026-09-0629LowActiveup
2026-09-0529LowActiveup
2026-09-0429LowActiveup
2026-09-0329LowActiveup
2026-09-0229LowActiveup
2026-09-0129LowActiveup
2026-08-3117LowActiveunknown
2026-08-3017LowActiveunknown
2026-08-2917LowActiveunknown
2026-08-2817LowActiveunknown
2026-08-2717LowActiveunknown
2026-08-2617LowActiveunknown
2026-08-2517LowActiveunknown
2026-08-2417LowActiveunknown
2026-08-2317LowActiveunknown
2026-08-2217LowActiveunknown
2026-08-2117LowActiveunknown
2026-08-2017LowActiveunknown
2026-08-1917LowActiveunknown
2026-08-1817LowActiveunknown
2026-08-1717LowActiveunknown
2026-08-1617LowActiveunknown
2026-08-1517LowActiveunknown
2026-08-1417LowActiveunknown
2026-08-1317LowActiveunknown
2026-08-1217LowActiveunknown
2026-08-1117LowActiveunknown
2026-08-1017LowActiveunknown
2026-08-0917LowActiveunknown
2026-08-0817LowActiveunknown
2026-08-0717LowActiveunknown
2026-08-0617LowActiveunknown
2026-08-0517LowActiveunknown
2026-08-0417LowActiveunknown
2026-08-0317LowActiveunknown
2026-08-0217LowActiveunknown
2026-08-0117LowActiveunknown
2026-07-3117LowActiveunknown
2026-07-3017LowActiveunknown
2026-07-2917LowActiveunknown
2026-07-2817LowActiveunknown
2026-07-2717LowActiveunknown
2026-07-2617LowActiveunknown
2026-07-2517LowActiveunknown
2026-07-2417LowActiveunknown
2026-07-2317LowActiveunknown
2026-07-2217LowActiveunknown
2026-07-2117LowActiveunknown
2026-07-2017LowActiveunknown
2026-07-1912LowActiveunknown

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 26, 2026
    Edited: entity class, resource type
  2. Aug 1, 2026
    Sato Hub began tracking this listing
  3. Jul 20, 2026
    Edited: deploy spec
  4. Jul 19, 2026
    Edited: chains supported
  5. Jul 19, 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.