Sato Hub
Score history

NanoParse

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

Score today

79

Change over 1d

0

Days measured

1

Days missed

0

Sato Score, daily

2026-10-14 → 2026-10-14
02550751002026-10-14: 79 (High)792026-10-142026-10-14

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.

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 & provenance6/15
15
Independent verification6/10
10

The observed record

1 check recorded, 1 in the rate window — too few to state a rate. 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-14: 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-1479HighEarlyup

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 14, 2026
    Listed on Sato Hub
  2. Oct 14, 2026
    Sato Hub began tracking this listing
  3. Oct 14, 2026
    Updated: description long

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.