Sato Hub
Score history

ETHSKILLS

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

Score today

35

Change over 109d

+23

Days measured

109

Days missed

0

Sato Score, daily

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

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

DateFromToChangeCause
2026-09-013235+3Sato Hub changed the scoring method
2026-07-141232+20Sato 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 & demo6/10
10
Listing transparency & provenance6/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-2935LowUnknownup
2026-10-2835LowUnknownup
2026-10-2735LowUnknownup
2026-10-2635LowUnknownup
2026-10-2535LowUnknownup
2026-10-2435LowUnknownup
2026-10-2335LowUnknownup
2026-10-2235LowUnknownup
2026-10-2135LowUnknownup
2026-10-2035LowUnknownup
2026-10-1935LowUnknownup
2026-10-1835LowUnknownup
2026-10-1735LowUnknownup
2026-10-1635LowUnknownup
2026-10-1535LowUnknownup
2026-10-1435LowUnknownup
2026-10-1335LowUnknownup
2026-10-1235LowUnknownup
2026-10-1135LowUnknownup
2026-10-1035LowUnknownup
2026-10-0935LowUnknownup
2026-10-0835LowUnknownup
2026-10-0735LowUnknownup
2026-10-0635LowUnknownup
2026-10-0535LowUnknownup
2026-10-0435LowUnknownup
2026-10-0335LowUnknownup
2026-10-0235LowUnknownup
2026-10-0135LowUnknownup
2026-09-3035LowUnknownup
2026-09-2935LowUnknownup
2026-09-2835LowUnknownup
2026-09-2735LowUnknownup
2026-09-2635LowUnknownup
2026-09-2535LowUnknownup
2026-09-2435LowUnknownup
2026-09-2335LowUnknownup
2026-09-2235LowUnknownup
2026-09-2135LowUnknownup
2026-09-2035LowUnknownup
2026-09-1935LowUnknownup
2026-09-1835LowUnknownup
2026-09-1735LowUnknownup
2026-09-1635LowUnknownup
2026-09-1535LowUnknownup
2026-09-1435LowUnknownup
2026-09-1335LowUnknownup
2026-09-1235LowUnknownup
2026-09-1135LowUnknownup
2026-09-1035LowUnknownup
2026-09-0935LowUnknownup
2026-09-0835LowUnknownup
2026-09-0735LowUnknownup
2026-09-0635LowUnknownup
2026-09-0535LowUnknownup
2026-09-0435LowUnknownup
2026-09-0335LowUnknownup
2026-09-0235LowUnknownup
2026-09-0135LowUnknownup
2026-08-3132LowUnknownup
2026-08-3032LowUnknownup
2026-08-2932LowUnknownup
2026-08-2832LowUnknownup
2026-08-2732LowUnknownup
2026-08-2632LowUnknownup
2026-08-2532LowUnknownup
2026-08-2432LowUnknownup
2026-08-2332LowUnknownup
2026-08-2232LowUnknownup
2026-08-2132LowUnknownup
2026-08-2032LowUnknownup
2026-08-1932LowUnknownup
2026-08-1832LowUnknownup
2026-08-1732LowUnknownup
2026-08-1632LowUnknownup
2026-08-1532LowUnknownup
2026-08-1432LowUnknownup
2026-08-1332LowUnknownup
2026-08-1232LowUnknownup
2026-08-1132LowUnknownup
2026-08-1032LowUnknownup
2026-08-0932LowUnknownup
2026-08-0832LowUnknownup
2026-08-0732LowUnknownup
2026-08-0632LowUnknownup
2026-08-0532LowUnknownup
2026-08-0432LowUnknownup
2026-08-0332LowUnknownup
2026-08-0232LowUnknownup
2026-08-0132LowUnknownup
2026-07-3132LowUnknownup
2026-07-3032LowUnknownup
2026-07-2932LowUnknownup
2026-07-2832LowUnknownup
2026-07-2732LowUnknownup
2026-07-2632LowUnknownup
2026-07-2532LowUnknownup
2026-07-2432LowUnknownup
2026-07-2332LowUnknownup
2026-07-2232LowUnknownup
2026-07-2132LowUnknownup
2026-07-2032LowUnknownup
2026-07-1932LowUnknownup
2026-07-1832LowUnknownup
2026-07-1732LowUnknownup
2026-07-1632LowUnknownup
2026-07-1532LowUnknownup
2026-07-1432LowUnknownup
2026-07-1312LowUnknownnot 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. Aug 1, 2026
    Sato Hub began tracking this listing
  2. Jul 14, 2026
    Enriched: docs url
  3. 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.
← Verification recordThis week’s moversDispute this score