Sato Hub
← Surf (asksurf.ai) verification record

Score history

Surf (asksurf.ai)

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

74

Change over 90d

0

Days measured

90

Days missed

4

Sato Score, daily

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

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

DateFromToChangeCause
2026-09-017174+3Sato Hub changed the scoring method
2026-08-268171-10the project
2026-07-247581+6the project
2026-07-207175+4Sato Hub changed the scoring method
2026-07-147271-1Sato Hub changed the scoring method
2026-07-128272-10the project
2026-06-257582+7Sato Hub changed the scoring method
2026-06-177475+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 & liveness25/35
35
Code transparency14/20
20
Interface verifiability8/10
10
Docs & demo10/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-1374HighActiveup
2026-09-1274HighActiveup
2026-09-1174HighActiveup
2026-09-1074HighActiveup
2026-09-0974HighActiveup
2026-09-0874HighActiveup
2026-09-0774HighActiveup
2026-09-0674HighActiveup
2026-09-0574HighActiveup
2026-09-0474HighActiveup
2026-09-0374HighActiveup
2026-09-0274HighActiveup
2026-09-0174HighActiveup
2026-08-3171HighActiveup
2026-08-3071HighActiveup
2026-08-2971HighActiveup
2026-08-2871HighActiveup
2026-08-2771HighActiveup
2026-08-2671HighActiveup
2026-08-2581HighActiveup
2026-08-2481HighActiveup
2026-08-2381HighActiveup
2026-08-2281HighActiveup
2026-08-2181HighActiveup
2026-08-2081HighActiveup
2026-08-1981HighActiveup
2026-08-1881HighActiveup
2026-08-1781HighActiveup
2026-08-1681HighActiveup
2026-08-1581HighActiveup
2026-08-1481HighActiveup
2026-08-1381HighActiveup
2026-08-1281HighActiveup
2026-08-1181HighActiveup
2026-08-1081HighActiveup
2026-08-0981HighActiveup
2026-08-0881HighActiveup
2026-08-0781HighActiveup
2026-08-0681HighActiveup
2026-08-0581HighActiveup
2026-08-0481HighActiveup
2026-08-0381HighActiveup
2026-08-0281HighActiveup
2026-08-0181HighActiveup
2026-07-3181HighActiveup
2026-07-3081HighActiveup
2026-07-2981HighActiveup
2026-07-2881HighActiveup
2026-07-2781HighActiveup
2026-07-2681HighActiveup
2026-07-2581HighActiveup
2026-07-2481HighActiveup
2026-07-2375HighActiveup
2026-07-2275HighActiveup
2026-07-2175HighActiveup
2026-07-2075HighActiveup
2026-07-1971HighActiveup
2026-07-1871HighActiveup
2026-07-1771HighActiveup
2026-07-1671HighActiveup
2026-07-1571HighActiveup
2026-07-1471HighActiveup
2026-07-1372HighActivenot checked
2026-07-1272HighActivenot checked
2026-07-1182HighActivenot checked
2026-07-1082HighActivenot checked
2026-07-0982HighActivenot checked
2026-07-0882HighActivenot checked
2026-07-0782HighActivenot checked
2026-07-0682HighActivenot checked
2026-07-0582HighActivenot checked
2026-07-0482HighActivenot checked
2026-07-0382HighActivenot checked
2026-07-0282HighActivenot checked
2026-07-0182HighActivenot checked
2026-06-3082HighActivenot checked
2026-06-2782HighActivenot checked
2026-06-2682HighActivenot checked
2026-06-2582HighActivenot checked
2026-06-2475HighActivenot checked
2026-06-2275HighActivenot checked
2026-06-2075HighActivenot checked
2026-06-1975HighActivenot checked
2026-06-1875HighActivenot checked
2026-06-1775HighActivenot checked
2026-06-1674HighActivenot checked
2026-06-1574HighActivenot checked
2026-06-1474HighActivenot checked
2026-06-1374HighActivenot checked
2026-06-1274HighActivenot 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. Sep 7, 2026
    Verified: deploy spec
  2. Jul 27, 2026
    New release published
  3. Jul 24, 2026
    New release published
  4. Jun 25, 2026
    Enriched: creator name, deployment options, has pricing, pricing +1 more
  5. Jun 25, 2026
    Auto-enriched: creator profile url, supported integrations
  6. 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