Sato Hub
OpenAI Codex verification record

Score history

OpenAI Codex

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

80

Change over 90d

+2

Days measured

90

Days missed

4

Sato Score, daily

2026-06-112026-09-13
02550751002026-06-25: Sato Hub changed the scoring method (78 → 86). Not a change by the project.2026-07-14: Sato Hub changed the scoring method (86 → 80). Not a change by the project.2026-06-12: 78 (High)2026-06-13: 78 (High)2026-06-14: 78 (High)2026-06-15: 78 (High)2026-06-16: 78 (High)2026-06-17: 78 (High)2026-06-18: 78 (High)2026-06-19: 78 (High)2026-06-20: 78 (High)2026-06-22: 78 (High)2026-06-24: 78 (High)2026-06-25: 86 (High)2026-06-26: 86 (High)2026-06-27: 86 (High)2026-06-30: 86 (High)2026-07-01: 86 (High)2026-07-02: 86 (High)2026-07-03: 86 (High)2026-07-04: 86 (High)2026-07-05: 86 (High)2026-07-06: 86 (High)2026-07-07: 86 (High)2026-07-08: 86 (High)2026-07-09: 86 (High)2026-07-10: 86 (High)2026-07-11: 86 (High)2026-07-12: 86 (High)2026-07-13: 86 (High)2026-07-14: 80 (High)2026-07-15: 80 (High)2026-07-16: 80 (High)2026-07-17: 80 (High)2026-07-18: 80 (High)2026-07-19: 80 (High)2026-07-20: 80 (High)2026-07-21: 80 (High)2026-07-22: 80 (High)2026-07-23: 80 (High)2026-07-24: 80 (High)2026-07-25: 80 (High)2026-07-26: 80 (High)2026-07-27: 80 (High)2026-07-28: 80 (High)2026-07-29: 80 (High)2026-07-30: 80 (High)2026-07-31: 80 (High)2026-08-01: 80 (High)2026-08-02: 80 (High)2026-08-03: 80 (High)2026-08-04: 80 (High)2026-08-05: 80 (High)2026-08-06: 80 (High)2026-08-07: 80 (High)2026-08-08: 80 (High)2026-08-09: 80 (High)2026-08-10: 80 (High)2026-08-11: 80 (High)2026-08-12: 80 (High)2026-08-13: 80 (High)2026-08-14: 80 (High)2026-08-15: 80 (High)2026-08-16: 80 (High)2026-08-17: 80 (High)2026-08-18: 80 (High)2026-08-19: 80 (High)2026-08-20: 80 (High)2026-08-21: 80 (High)2026-08-22: 80 (High)2026-08-23: 80 (High)2026-08-24: 80 (High)2026-08-25: 80 (High)2026-08-26: 80 (High)2026-08-27: 80 (High)2026-08-28: 80 (High)2026-08-29: 80 (High)2026-08-30: 80 (High)2026-08-31: 80 (High)2026-09-01: 80 (High)2026-09-02: 80 (High)2026-09-03: 80 (High)2026-09-04: 80 (High)2026-09-05: 80 (High)2026-09-06: 80 (High)2026-09-07: 80 (High)2026-09-08: 80 (High)2026-09-09: 80 (High)2026-09-10: 80 (High)2026-09-11: 80 (High)2026-09-12: 80 (High)2026-09-13: 80 (High)7886802026-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, 2 caused by a revision of the scoring method.

DateFromToChangeCause
2026-07-148680-6Sato Hub changed the scoring method
2026-06-257886+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 transparency16/20
20
Interface verifiability0/10
10
Docs & demo6/10
10
Listing transparency & provenance15/15
15
Independent verification8/10
10

The observed record

21% 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: failed, unattributable2026-08-28: failed, unattributable2026-08-29: failed, unattributable2026-08-30: failed, unattributable2026-08-31: failed, unattributable2026-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-1380HighActiveup
2026-09-1280HighActiveup
2026-09-1180HighActiveup
2026-09-1080HighActiveup
2026-09-0980HighActiveup
2026-09-0880HighActiveup
2026-09-0780HighActiveup
2026-09-0680HighActiveup
2026-09-0580HighActiveup
2026-09-0480HighActiveup
2026-09-0380HighActiveup
2026-09-0280HighActiveup
2026-09-0180HighActiveup
2026-08-3180HighActiveunknown
2026-08-3080HighActiveunknown
2026-08-2980HighActiveunknown
2026-08-2880HighActiveunknown
2026-08-2780HighActiveunknown
2026-08-2680HighActiveunknown
2026-08-2580HighActiveunknown
2026-08-2480HighActiveunknown
2026-08-2380HighActiveunknown
2026-08-2280HighActiveunknown
2026-08-2180HighActiveunknown
2026-08-2080HighActiveunknown
2026-08-1980HighActiveunknown
2026-08-1880HighActiveunknown
2026-08-1780HighActiveunknown
2026-08-1680HighActiveunknown
2026-08-1580HighActiveunknown
2026-08-1480HighActiveunknown
2026-08-1380HighActiveunknown
2026-08-1280HighActiveunknown
2026-08-1180HighActiveunknown
2026-08-1080HighActiveunknown
2026-08-0980HighActiveunknown
2026-08-0880HighActiveunknown
2026-08-0780HighActiveunknown
2026-08-0680HighActiveunknown
2026-08-0580HighActiveunknown
2026-08-0480HighActiveunknown
2026-08-0380HighActiveunknown
2026-08-0280HighActiveunknown
2026-08-0180HighActiveunknown
2026-07-3180HighActiveunknown
2026-07-3080HighActiveunknown
2026-07-2980HighActiveunknown
2026-07-2880HighActiveunknown
2026-07-2780HighActiveunknown
2026-07-2680HighActiveunknown
2026-07-2580HighActiveunknown
2026-07-2480HighActiveunknown
2026-07-2380HighActiveunknown
2026-07-2280HighActiveunknown
2026-07-2180HighActiveunknown
2026-07-2080HighActiveunknown
2026-07-1980HighActiveunknown
2026-07-1880HighActiveunknown
2026-07-1780HighActiveunknown
2026-07-1680HighActiveunknown
2026-07-1580HighActiveunknown
2026-07-1480HighActiveunknown
2026-07-1386HighActivenot checked
2026-07-1286HighActivenot checked
2026-07-1186HighActivenot checked
2026-07-1086HighActivenot checked
2026-07-0986HighActivenot checked
2026-07-0886HighActivenot checked
2026-07-0786HighActivenot checked
2026-07-0686HighActivenot checked
2026-07-0586HighActivenot checked
2026-07-0486HighActivenot checked
2026-07-0386HighActivenot checked
2026-07-0286HighActivenot checked
2026-07-0186HighActivenot checked
2026-06-3086HighActivenot checked
2026-06-2786HighActivenot checked
2026-06-2686HighActivenot checked
2026-06-2586HighActivenot checked
2026-06-2478HighActivenot checked
2026-06-2278HighActivenot checked
2026-06-2078HighActivenot checked
2026-06-1978HighActivenot checked
2026-06-1878HighActivenot checked
2026-06-1778HighActivenot checked
2026-06-1678HighActivenot checked
2026-06-1578HighActivenot checked
2026-06-1478HighActivenot checked
2026-06-1378HighActivenot checked
2026-06-1278HighActivenot 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 11, 2026
    New release published
  2. Sep 10, 2026
    New release published
  3. Jul 22, 2026
    Crossed 100k GitHub stars
    98267 → 100584.
  4. Jul 14, 2026
    Enriched: is agent
  5. Jun 25, 2026
    Auto-enriched: creator name, creator profile url, deployment options, supported integrations +1 more
  6. Jun 16, 2026
    Edited: deploy spec
  7. Jun 13, 2026
    70 releases tracked
    Showing the 2 most recent. Full release history is retained in the listing record.
  8. 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.