Sato Hub
← Jupiter verification record

Score history

Jupiter

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

84

Change over 90d

+11

Days measured

90

Days missed

4

Sato Score, daily

2026-06-11 → 2026-09-13
02550751002026-06-25: Sato Hub changed the scoring method (73 → 81). Not a change by the project.2026-07-14: Sato Hub changed the scoring method (81 → 76). Not a change by the project.2026-07-20: Sato Hub changed the scoring method (76 → 84). Not a change by the project.2026-06-12: 73 (High)2026-06-13: 73 (High)2026-06-14: 73 (High)2026-06-15: 73 (High)2026-06-16: 73 (High)2026-06-17: 73 (High)2026-06-18: 73 (High)2026-06-19: 73 (High)2026-06-20: 73 (High)2026-06-22: 73 (High)2026-06-24: 73 (High)2026-06-25: 81 (High)2026-06-26: 81 (High)2026-06-27: 81 (High)2026-06-30: 81 (High)2026-07-01: 81 (High)2026-07-02: 81 (High)2026-07-03: 81 (High)2026-07-04: 81 (High)2026-07-05: 81 (High)2026-07-06: 81 (High)2026-07-07: 81 (High)2026-07-08: 81 (High)2026-07-09: 81 (High)2026-07-10: 81 (High)2026-07-11: 81 (High)2026-07-12: 81 (High)2026-07-13: 81 (High)2026-07-14: 76 (High)2026-07-15: 76 (High)2026-07-16: 76 (High)2026-07-17: 76 (High)2026-07-18: 76 (High)2026-07-19: 76 (High)2026-07-20: 84 (High)2026-07-21: 84 (High)2026-07-22: 84 (High)2026-07-23: 84 (High)2026-07-24: 84 (High)2026-07-25: 84 (High)2026-07-26: 84 (High)2026-07-27: 84 (High)2026-07-28: 84 (High)2026-07-29: 84 (High)2026-07-30: 84 (High)2026-07-31: 84 (High)2026-08-01: 84 (High)2026-08-02: 84 (High)2026-08-03: 84 (High)2026-08-04: 84 (High)2026-08-05: 84 (High)2026-08-06: 84 (High)2026-08-07: 84 (High)2026-08-08: 84 (High)2026-08-09: 84 (High)2026-08-10: 84 (High)2026-08-11: 84 (High)2026-08-12: 84 (High)2026-08-13: 84 (High)2026-08-14: 84 (High)2026-08-15: 84 (High)2026-08-16: 84 (High)2026-08-17: 84 (High)2026-08-18: 84 (High)2026-08-19: 84 (High)2026-08-20: 84 (High)2026-08-21: 84 (High)2026-08-22: 84 (High)2026-08-23: 84 (High)2026-08-24: 84 (High)2026-08-25: 84 (High)2026-08-26: 84 (High)2026-08-27: 84 (High)2026-08-28: 84 (High)2026-08-29: 84 (High)2026-08-30: 84 (High)2026-08-31: 84 (High)2026-09-01: 84 (High)2026-09-02: 84 (High)2026-09-03: 84 (High)2026-09-04: 84 (High)2026-09-05: 84 (High)2026-09-06: 84 (High)2026-09-07: 84 (High)2026-09-08: 84 (High)2026-09-09: 84 (High)2026-09-10: 84 (High)2026-09-11: 84 (High)2026-09-12: 84 (High)2026-09-13: 84 (High)7384842026-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

0 changes attributable to the project, 3 caused by a revision of the scoring method.

DateFromToChangeCause
2026-07-207684+8Sato Hub changed the scoring method
2026-07-148176-5Sato Hub changed the scoring method
2026-06-257381+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 transparency12/20
20
Interface verifiability8/10
10
Docs & demo6/10
10
Listing transparency & provenance15/15
15
Independent verification8/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-1384HighActiveup
2026-09-1284HighActiveup
2026-09-1184HighActiveup
2026-09-1084HighActiveup
2026-09-0984HighActiveup
2026-09-0884HighActiveup
2026-09-0784HighActiveup
2026-09-0684HighActiveup
2026-09-0584HighActiveup
2026-09-0484HighActiveup
2026-09-0384HighActiveup
2026-09-0284HighActiveup
2026-09-0184HighActiveup
2026-08-3184HighActiveup
2026-08-3084HighActiveup
2026-08-2984HighActiveup
2026-08-2884HighActiveup
2026-08-2784HighActiveup
2026-08-2684HighActiveup
2026-08-2584HighActiveup
2026-08-2484HighActiveup
2026-08-2384HighActiveup
2026-08-2284HighActiveup
2026-08-2184HighActiveup
2026-08-2084HighActiveup
2026-08-1984HighActiveup
2026-08-1884HighActiveup
2026-08-1784HighActiveup
2026-08-1684HighActiveup
2026-08-1584HighActiveup
2026-08-1484HighActiveup
2026-08-1384HighActiveup
2026-08-1284HighActiveup
2026-08-1184HighActiveup
2026-08-1084HighActiveup
2026-08-0984HighActiveup
2026-08-0884HighActiveup
2026-08-0784HighActiveup
2026-08-0684HighActiveup
2026-08-0584HighActiveup
2026-08-0484HighActiveup
2026-08-0384HighActiveup
2026-08-0284HighActiveup
2026-08-0184HighActiveup
2026-07-3184HighActiveup
2026-07-3084HighActiveup
2026-07-2984HighActiveup
2026-07-2884HighActiveup
2026-07-2784HighActiveup
2026-07-2684HighActiveup
2026-07-2584HighActiveup
2026-07-2484HighActiveup
2026-07-2384HighActiveup
2026-07-2284HighActiveup
2026-07-2184HighActiveup
2026-07-2084HighActiveup
2026-07-1976HighActiveup
2026-07-1876HighActiveup
2026-07-1776HighActiveup
2026-07-1676HighActiveup
2026-07-1576HighActiveup
2026-07-1476HighActiveup
2026-07-1381HighActivenot checked
2026-07-1281HighActivenot checked
2026-07-1181HighActivenot checked
2026-07-1081HighActivenot checked
2026-07-0981HighActivenot checked
2026-07-0881HighActivenot checked
2026-07-0781HighActivenot checked
2026-07-0681HighActivenot checked
2026-07-0581HighActivenot checked
2026-07-0481HighActivenot checked
2026-07-0381HighActivenot checked
2026-07-0281HighActivenot checked
2026-07-0181HighActivenot checked
2026-06-3081HighActivenot checked
2026-06-2781HighActivenot checked
2026-06-2681HighActivenot checked
2026-06-2581HighActivenot checked
2026-06-2473HighActivenot checked
2026-06-2273HighActivenot checked
2026-06-2073HighActivenot checked
2026-06-1973HighActivenot checked
2026-06-1873HighActivenot checked
2026-06-1773HighActivenot checked
2026-06-1673HighActivenot checked
2026-06-1573HighActivenot checked
2026-06-1473HighActivenot checked
2026-06-1373HighActivenot checked
2026-06-1273HighActivenot checked
2026-06-11unknown—Activenot 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. Jul 21, 2026
    Verified: deploy spec
  2. Jun 25, 2026
    Enriched: marketplace notes
  3. Jun 25, 2026
    Auto-enriched: creator name, deployment options, supported integrations, tags
  4. 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.
← Verification recordThis week’s moversDispute this score