Sato Hub
AgentNode verification record

Score history

AgentNode

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

75

Change over 90d

+4

Days measured

90

Days missed

4

Sato Score, daily

2026-06-112026-09-13
02550751002026-06-25: Sato Hub changed the scoring method (71 → 79). Not a change by the project.2026-07-14: Sato Hub changed the scoring method (79 → 72). Not a change by the project.2026-09-01: Sato Hub changed the scoring method (62 → 65). Not a change by the project.2026-06-12: 71 (High)2026-06-13: 71 (High)2026-06-14: 71 (High)2026-06-15: 71 (High)2026-06-16: 71 (High)2026-06-17: 71 (High)2026-06-18: 71 (High)2026-06-19: 71 (High)2026-06-20: 71 (High)2026-06-22: 71 (High)2026-06-24: 71 (High)2026-06-25: 79 (High)2026-06-26: 79 (High)2026-06-27: 79 (High)2026-06-30: 79 (High)2026-07-01: 79 (High)2026-07-02: 79 (High)2026-07-03: 79 (High)2026-07-04: 79 (High)2026-07-05: 79 (High)2026-07-06: 79 (High)2026-07-07: 79 (High)2026-07-08: 79 (High)2026-07-09: 79 (High)2026-07-10: 79 (High)2026-07-11: 79 (High)2026-07-12: 79 (High)2026-07-13: 79 (High)2026-07-14: 72 (High)2026-07-15: 72 (High)2026-07-16: 72 (High)2026-07-17: 72 (High)2026-07-18: 72 (High)2026-07-19: 72 (High)2026-07-20: 72 (High)2026-07-21: 72 (High)2026-07-22: 72 (High)2026-07-23: 72 (High)2026-07-24: 72 (High)2026-07-25: 72 (High)2026-07-26: 72 (High)2026-07-27: 72 (High)2026-07-28: 72 (High)2026-07-29: 72 (High)2026-07-30: 72 (High)2026-07-31: 72 (High)2026-08-01: 72 (High)2026-08-02: 72 (High)2026-08-03: 72 (High)2026-08-04: 72 (High)2026-08-05: 72 (High)2026-08-06: 72 (High)2026-08-07: 72 (High)2026-08-08: 72 (High)2026-08-09: 72 (High)2026-08-10: 72 (High)2026-08-11: 72 (High)2026-08-12: 72 (High)2026-08-13: 72 (High)2026-08-14: 72 (High)2026-08-15: 72 (High)2026-08-16: 72 (High)2026-08-17: 72 (High)2026-08-18: 72 (High)2026-08-19: 72 (High)2026-08-20: 72 (High)2026-08-21: 72 (High)2026-08-22: 72 (High)2026-08-23: 72 (High)2026-08-24: 62 (Medium)2026-08-25: 62 (Medium)2026-08-26: 62 (Medium)2026-08-27: 62 (Medium)2026-08-28: 62 (Medium)2026-08-29: 62 (Medium)2026-08-30: 62 (Medium)2026-08-31: 62 (Medium)2026-09-01: 65 (Medium)2026-09-02: 65 (Medium)2026-09-03: 75 (High)2026-09-04: 75 (High)2026-09-05: 75 (High)2026-09-06: 75 (High)2026-09-07: 75 (High)2026-09-08: 75 (High)2026-09-09: 75 (High)2026-09-10: 75 (High)2026-09-11: 75 (High)2026-09-12: 75 (High)2026-09-13: 75 (High)7179752026-06-122026-09-13

4 days in this span have no reading; the line breaks there rather than joining across them. 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, 3 caused by a revision of the scoring method.

DateFromToChangeCause
2026-09-036575+10the project
2026-09-016265+3Sato Hub changed the scoring method
2026-08-247262-10the project
2026-07-147972-7Sato Hub changed the scoring method
2026-06-257179+8Sato 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 & liveness35/35
35
Code transparency17/20
20
Interface verifiability0/10
10
Docs & demo6/10
10
Listing transparency & provenance14/15
15
Independent verification3/10
10

The observed record

100% 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: 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 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-1375HighActiveup
2026-09-1275HighActiveup
2026-09-1175HighActiveup
2026-09-1075HighActiveup
2026-09-0975HighActiveup
2026-09-0875HighActiveup
2026-09-0775HighActiveup
2026-09-0675HighActiveup
2026-09-0575HighActiveup
2026-09-0475HighActiveup
2026-09-0375HighActiveup
2026-09-0265MediumActiveup
2026-09-0165MediumActiveup
2026-08-3162MediumActiveup
2026-08-3062MediumActiveup
2026-08-2962MediumActiveup
2026-08-2862MediumActiveup
2026-08-2762MediumActiveup
2026-08-2662MediumActiveup
2026-08-2562MediumActiveup
2026-08-2462MediumActiveup
2026-08-2372HighActiveup
2026-08-2272HighActiveup
2026-08-2172HighActiveup
2026-08-2072HighActiveup
2026-08-1972HighActiveup
2026-08-1872HighActiveup
2026-08-1772HighActiveup
2026-08-1672HighActiveup
2026-08-1572HighActiveup
2026-08-1472HighActiveup
2026-08-1372HighActiveup
2026-08-1272HighActiveup
2026-08-1172HighActiveup
2026-08-1072HighActiveup
2026-08-0972HighActiveup
2026-08-0872HighActiveup
2026-08-0772HighActiveup
2026-08-0672HighActiveup
2026-08-0572HighActiveup
2026-08-0472HighActiveup
2026-08-0372HighActiveup
2026-08-0272HighActiveup
2026-08-0172HighActiveup
2026-07-3172HighActiveup
2026-07-3072HighActiveup
2026-07-2972HighActiveup
2026-07-2872HighActiveup
2026-07-2772HighActiveup
2026-07-2672HighActiveup
2026-07-2572HighActiveup
2026-07-2472HighActiveup
2026-07-2372HighActiveup
2026-07-2272HighActiveup
2026-07-2172HighActiveup
2026-07-2072HighActiveup
2026-07-1972HighActiveup
2026-07-1872HighActiveup
2026-07-1772HighActiveup
2026-07-1672HighActiveup
2026-07-1572HighActiveup
2026-07-1472HighActiveup
2026-07-1379HighActivenot checked
2026-07-1279HighActivenot checked
2026-07-1179HighActivenot checked
2026-07-1079HighActivenot checked
2026-07-0979HighActivenot checked
2026-07-0879HighActivenot checked
2026-07-0779HighActivenot checked
2026-07-0679HighActivenot checked
2026-07-0579HighActivenot checked
2026-07-0479HighActivenot checked
2026-07-0379HighActivenot checked
2026-07-0279HighActivenot checked
2026-07-0179HighActivenot checked
2026-06-3079HighActivenot checked
2026-06-2779HighActivenot checked
2026-06-2679HighActivenot checked
2026-06-2579HighActivenot checked
2026-06-2471HighActivenot checked
2026-06-2271HighActivenot checked
2026-06-2071HighActivenot checked
2026-06-1971HighActivenot checked
2026-06-1871HighActivenot checked
2026-06-1771HighActivenot checked
2026-06-1671HighActivenot checked
2026-06-1571HighActivenot checked
2026-06-1471HighActivenot checked
2026-06-1371HighActivenot checked
2026-06-1271HighActivenot checked
2026-06-11unknownActivenot 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. Sep 7, 2026
    New release published
  2. Sep 3, 2026
    Sato Score tier: Medium → High
    Score 65 → 75.
  3. Sep 2, 2026
    New release published
  4. Aug 24, 2026
    Sato Score tier: High → Medium
    Score 72 → 62.
  5. Jul 20, 2026
    Edited: deploy spec
  6. Jul 3, 2026
    8 releases tracked
    Showing the 2 most recent. Full release history is retained in the listing record.
  7. Jun 25, 2026
    Enriched: creator profile url
  8. Jun 24, 2026
    Auto-enriched: creator name, supported integrations, deployment options, tags +1 more
  9. Jun 12, 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.