Sato Hub
← dRPC Agent Skills verification record

Score history

dRPC Agent Skills

Every Sato Hub Sato Score reading we have captured for this listing, one per day, each dated. Days we changed the scoring method are marked separately from days the project moved. How open, active and verifiable — not a safety, quality, or returns grade.

Score today

56

Change over 62d

-4

Days measured

62

Days missed

0

Sato Score, daily

2026-07-14 → 2026-09-13
02550751002026-07-15: Sato Hub changed the scoring method (60 → 61). Not a change by the project.2026-07-14: 60 (Medium)2026-07-15: 61 (Medium)2026-07-16: 49 (Medium)2026-07-17: 49 (Medium)2026-07-18: 49 (Medium)2026-07-19: 49 (Medium)2026-07-20: 49 (Medium)2026-07-21: 49 (Medium)2026-07-22: 49 (Medium)2026-07-23: 49 (Medium)2026-07-24: 49 (Medium)2026-07-25: 49 (Medium)2026-07-26: 49 (Medium)2026-07-27: 49 (Medium)2026-07-28: 49 (Medium)2026-07-29: 49 (Medium)2026-07-30: 49 (Medium)2026-07-31: 49 (Medium)2026-08-01: 49 (Medium)2026-08-02: 49 (Medium)2026-08-03: 49 (Medium)2026-08-04: 49 (Medium)2026-08-05: 49 (Medium)2026-08-06: 49 (Medium)2026-08-07: 49 (Medium)2026-08-08: 49 (Medium)2026-08-09: 49 (Medium)2026-08-10: 49 (Medium)2026-08-11: 49 (Medium)2026-08-12: 49 (Medium)2026-08-13: 49 (Medium)2026-08-14: 49 (Medium)2026-08-15: 49 (Medium)2026-08-16: 49 (Medium)2026-08-17: 49 (Medium)2026-08-18: 49 (Medium)2026-08-19: 49 (Medium)2026-08-20: 49 (Medium)2026-08-21: 49 (Medium)2026-08-22: 49 (Medium)2026-08-23: 49 (Medium)2026-08-24: 49 (Medium)2026-08-25: 49 (Medium)2026-08-26: 49 (Medium)2026-08-27: 56 (Medium)2026-08-28: 56 (Medium)2026-08-29: 56 (Medium)2026-08-30: 56 (Medium)2026-08-31: 56 (Medium)2026-09-01: 56 (Medium)2026-09-02: 56 (Medium)2026-09-03: 56 (Medium)2026-09-04: 56 (Medium)2026-09-05: 56 (Medium)2026-09-06: 56 (Medium)2026-09-07: 56 (Medium)2026-09-08: 56 (Medium)2026-09-09: 56 (Medium)2026-09-10: 56 (Medium)2026-09-11: 56 (Medium)2026-09-12: 56 (Medium)2026-09-13: 56 (Medium)6061562026-07-142026-09-13

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

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

DateFromToChangeCause
2026-08-274956+7the project
2026-07-166149-12the project
2026-07-156061+1Sato 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 transparency18/20
20
Interface verifiability0/10
10
Docs & demo6/10
10
Listing transparency & provenance12/15
15
Independent verification0/10
10

The observed record

29% of Sato Hub's own daily checks succeeded over 62 checks. This is the share of OUR checks that succeeded. It is not uptime: a failed check can be on our side, and before 2026-09-01 no failure recorded why.

2026-07-14: failed, unattributable2026-07-15: failed, unattributable2026-07-16: failed, unattributable2026-07-17: failed, unattributable2026-07-18: failed, unattributable2026-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: 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 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-09-1356MediumActiveup
2026-09-1256MediumActiveup
2026-09-1156MediumActiveup
2026-09-1056MediumActiveup
2026-09-0956MediumActiveup
2026-09-0856MediumActiveup
2026-09-0756MediumActiveup
2026-09-0656MediumActiveup
2026-09-0556MediumActiveup
2026-09-0456MediumActiveup
2026-09-0356MediumActiveup
2026-09-0256MediumActiveup
2026-09-0156MediumActiveup
2026-08-3156MediumActiveup
2026-08-3056MediumActiveup
2026-08-2956MediumActiveup
2026-08-2856MediumActiveup
2026-08-2756MediumActiveup
2026-08-2649MediumActiveunknown
2026-08-2549MediumActiveunknown
2026-08-2449MediumActiveunknown
2026-08-2349MediumActiveunknown
2026-08-2249MediumActiveunknown
2026-08-2149MediumActiveunknown
2026-08-2049MediumActiveunknown
2026-08-1949MediumActiveunknown
2026-08-1849MediumActiveunknown
2026-08-1749MediumActiveunknown
2026-08-1649MediumActiveunknown
2026-08-1549MediumActiveunknown
2026-08-1449MediumActiveunknown
2026-08-1349MediumActiveunknown
2026-08-1249MediumActiveunknown
2026-08-1149MediumActiveunknown
2026-08-1049MediumActiveunknown
2026-08-0949MediumActiveunknown
2026-08-0849MediumActiveunknown
2026-08-0749MediumActiveunknown
2026-08-0649MediumActiveunknown
2026-08-0549MediumActiveunknown
2026-08-0449MediumActiveunknown
2026-08-0349MediumActiveunknown
2026-08-0249MediumActiveunknown
2026-08-0149MediumActiveunknown
2026-07-3149MediumActiveunknown
2026-07-3049MediumActiveunknown
2026-07-2949MediumActiveunknown
2026-07-2849MediumActiveunknown
2026-07-2749MediumActiveunknown
2026-07-2649MediumActiveunknown
2026-07-2549MediumActiveunknown
2026-07-2449MediumActiveunknown
2026-07-2349MediumActiveunknown
2026-07-2249MediumActiveunknown
2026-07-2149MediumActiveunknown
2026-07-2049MediumActiveunknown
2026-07-1949MediumActiveunknown
2026-07-1849MediumActiveunknown
2026-07-1749MediumActiveunknown
2026-07-1649MediumActiveunknown
2026-07-1561MediumActiveunknown
2026-07-1460MediumActiveunknown

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. Jul 14, 2026
    Enriched: deployment options
  2. Jul 14, 2026
    Auto-enriched: supported integrations
  3. Jul 14, 2026
    Listed on Sato Hub
  4. Jul 14, 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