Sato Hub
Score history

Yelden (YAAF)

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

Score today

63

Change over 46d

+18

Days measured

46

Days missed

0

Sato Score, daily

2026-10-08 → 2026-11-22
02550751002026-10-08: 45 (Medium)2026-10-09: 45 (Medium)2026-10-10: 45 (Medium)2026-10-11: 45 (Medium)2026-10-12: 45 (Medium)2026-10-13: 45 (Medium)2026-10-14: 45 (Medium)2026-10-15: 45 (Medium)2026-10-16: 45 (Medium)2026-10-17: 45 (Medium)2026-10-18: 45 (Medium)2026-10-19: 60 (Medium)2026-10-20: 60 (Medium)2026-10-21: 60 (Medium)2026-10-22: 61 (Medium)2026-10-23: 61 (Medium)2026-10-24: 61 (Medium)2026-10-25: 61 (Medium)2026-10-26: 61 (Medium)2026-10-27: 61 (Medium)2026-10-28: 61 (Medium)2026-10-29: 61 (Medium)2026-10-30: 61 (Medium)2026-10-31: 61 (Medium)2026-11-01: 61 (Medium)2026-11-02: 61 (Medium)2026-11-03: 61 (Medium)2026-11-04: 63 (Medium)2026-11-05: 63 (Medium)2026-11-06: 63 (Medium)2026-11-07: 63 (Medium)2026-11-08: 63 (Medium)2026-11-09: 63 (Medium)2026-11-10: 63 (Medium)2026-11-11: 63 (Medium)2026-11-12: 63 (Medium)2026-11-13: 63 (Medium)2026-11-14: 63 (Medium)2026-11-15: 63 (Medium)2026-11-16: 63 (Medium)2026-11-17: 63 (Medium)2026-11-18: 63 (Medium)2026-11-19: 63 (Medium)2026-11-20: 63 (Medium)2026-11-21: 63 (Medium)2026-11-22: 63 (Medium)4563632026-10-082026-11-22

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-046163+2the project
2026-10-226061+1the project
2026-10-194560+15the 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 verifiability0/10
10
Docs & demo0/10
10
Listing transparency & provenance9/15
15
Independent verification3/10
10

The observed record

100% of 46 daily checks since 2026-10-08 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-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: answered our check2026-11-20: answered our check2026-11-21: answered our check2026-11-22: 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-11-2263MediumEarlyup
2026-11-2163MediumEarlyup
2026-11-2063MediumEarlyup
2026-11-1963MediumEarlyup
2026-11-1863MediumEarlyup
2026-11-1763MediumEarlyup
2026-11-1663MediumEarlyup
2026-11-1563MediumEarlyup
2026-11-1463MediumEarlyup
2026-11-1363MediumEarlyup
2026-11-1263MediumEarlyup
2026-11-1163MediumEarlyup
2026-11-1063MediumEarlyup
2026-11-0963MediumEarlyup
2026-11-0863MediumEarlyup
2026-11-0763MediumEarlyup
2026-11-0663MediumEarlyup
2026-11-0563MediumEarlyup
2026-11-0463MediumEarlyup
2026-11-0361MediumEarlyup
2026-11-0261MediumEarlyup
2026-11-0161MediumEarlyup
2026-10-3161MediumEarlyup
2026-10-3061MediumEarlyup
2026-10-2961MediumEarlyup
2026-10-2861MediumEarlyup
2026-10-2761MediumEarlyup
2026-10-2661MediumEarlyup
2026-10-2561MediumEarlyup
2026-10-2461MediumEarlyup
2026-10-2361MediumEarlyup
2026-10-2261MediumEarlyup
2026-10-2160MediumEarlyup
2026-10-2060MediumEarlyup
2026-10-1960MediumEarlyup
2026-10-1845MediumEarlyup
2026-10-1745MediumEarlyup
2026-10-1645MediumEarlyup
2026-10-1545MediumEarlyup
2026-10-1445MediumEarlyup
2026-10-1345MediumEarlyup
2026-10-1245MediumEarlyup
2026-10-1145MediumEarlyup
2026-10-1045MediumEarlyup
2026-10-0945MediumEarlyup
2026-10-0845MediumEarlyup

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 8, 2026
    Auto-enriched: creator name, x url
  2. Oct 8, 2026
    Sato Hub began tracking this listing

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.