Sato Hub
Score history

Forta Risk Graph MCP

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

Score today

54

Change over 45d

-6

Days measured

45

Days missed

0

Sato Score, daily

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

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-10-296454-10the project
2026-09-256364+1the project
2026-09-246063+3the 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 & liveness25/35
35
Code transparency13/20
20
Interface verifiability0/10
10
Docs & demo6/10
10
Listing transparency & provenance10/15
15
Independent verification0/10
10

The observed record

0% of 45 daily checks since 2026-09-22 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-09-22: the host answered with an error2026-09-23: failed on our side — not attributable to the project2026-09-24: failed on our side — not attributable to the project2026-09-25: failed on our side — not attributable to the project2026-09-26: failed on our side — not attributable to the project2026-09-27: failed on our side — not attributable to the project2026-09-28: failed on our side — not attributable to the project2026-09-29: failed on our side — not attributable to the project2026-09-30: failed on our side — not attributable to the project2026-10-01: failed on our side — not attributable to the project2026-10-02: failed on our side — not attributable to the project2026-10-03: failed on our side — not attributable to the project2026-10-04: failed on our side — not attributable to the project2026-10-05: failed on our side — not attributable to the project2026-10-06: failed on our side — not attributable to the project2026-10-07: failed on our side — not attributable to the project2026-10-08: failed on our side — not attributable to the project2026-10-09: failed on our side — not attributable to the project2026-10-10: failed on our side — not attributable to the project2026-10-11: failed on our side — not attributable to the project2026-10-12: failed on our side — not attributable to the project2026-10-13: failed on our side — not attributable to the project2026-10-14: failed on our side — not attributable to the project2026-10-15: failed on our side — not attributable to the project2026-10-16: failed on our side — not attributable to the project2026-10-17: failed on our side — not attributable to the project2026-10-18: failed on our side — not attributable to the project2026-10-19: failed on our side — not attributable to the project2026-10-20: failed on our side — not attributable to the project2026-10-21: failed on our side — not attributable to the project2026-10-22: failed on our side — not attributable to the project2026-10-23: failed on our side — not attributable to the project2026-10-24: failed on our side — not attributable to the project2026-10-25: failed on our side — not attributable to the project2026-10-26: failed on our side — not attributable to the project2026-10-27: failed on our side — not attributable to the project2026-10-28: failed on our side — not attributable to the project2026-10-29: failed on our side — not attributable to the project2026-10-30: failed on our side — not attributable to the project2026-10-31: failed on our side — not attributable to the project2026-11-01: failed on our side — not attributable to the project2026-11-02: failed on our side — not attributable to the project2026-11-03: failed on our side — not attributable to the project2026-11-04: failed on our side — not attributable to the project2026-11-05: failed on our side — not attributable to the project
  • 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-0554MediumEarlyinconclusive
2026-11-0454MediumEarlyinconclusive
2026-11-0354MediumEarlyinconclusive
2026-11-0254MediumEarlyinconclusive
2026-11-0154MediumEarlyinconclusive
2026-10-3154MediumEarlyinconclusive
2026-10-3054MediumEarlyinconclusive
2026-10-2954MediumEarlyinconclusive
2026-10-2864MediumEarlyinconclusive
2026-10-2764MediumEarlyinconclusive
2026-10-2664MediumEarlyinconclusive
2026-10-2564MediumEarlyinconclusive
2026-10-2464MediumEarlyinconclusive
2026-10-2364MediumEarlyinconclusive
2026-10-2264MediumEarlyinconclusive
2026-10-2164MediumEarlyinconclusive
2026-10-2064MediumEarlyinconclusive
2026-10-1964MediumEarlyinconclusive
2026-10-1864MediumEarlyinconclusive
2026-10-1764MediumEarlyinconclusive
2026-10-1664MediumEarlyinconclusive
2026-10-1564MediumEarlyinconclusive
2026-10-1464MediumEarlyinconclusive
2026-10-1364MediumEarlyinconclusive
2026-10-1264MediumEarlyinconclusive
2026-10-1164MediumEarlyinconclusive
2026-10-1064MediumEarlyinconclusive
2026-10-0964MediumEarlyinconclusive
2026-10-0864MediumEarlyinconclusive
2026-10-0764MediumEarlyinconclusive
2026-10-0664MediumEarlyinconclusive
2026-10-0564MediumEarlyinconclusive
2026-10-0464MediumEarlyinconclusive
2026-10-0364MediumEarlyinconclusive
2026-10-0264MediumEarlyinconclusive
2026-10-0164MediumEarlyinconclusive
2026-09-3064MediumEarlyinconclusive
2026-09-2964MediumEarlyinconclusive
2026-09-2864MediumEarlyinconclusive
2026-09-2764MediumEarlyinconclusive
2026-09-2664MediumEarlyinconclusive
2026-09-2564MediumEarlyinconclusive
2026-09-2463MediumEarlyinconclusive
2026-09-2360MediumEarlyinconclusive
2026-09-2260MediumEarlydown

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 25, 2026
    Edited: deploy spec
  2. Sep 24, 2026
    Auto-enriched: chains supported, supported integrations
  3. Sep 22, 2026
    Listed on Sato Hub
  4. Sep 22, 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.
← Verification recordThis week’s moversDispute this score