Score history

OpenZeppelin MCP

Name: OpenZeppelin MCP — Sato Score daily history
Creator: Sato Hub
License: https://creativecommons.org/licenses/by/4.0/

One dated Sato Score reading per day. Days we changed the scoring method are marked. Not a safety or returns grade.

Score today

Change over 109d

+25

Days measured

109

Days missed

Sato Score, daily

2026-07-13 → 2026-10-29

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

1 change attributable to the project, 3 caused by a revision of the scoring method.

Date	From	To	Change	Cause
2026-09-22	30	38	+8	the project
2026-09-01	27	30	+3	Sato Hub changed the scoring method
2026-07-20	26	27	+1	Sato Hub changed the scoring method
2026-07-14	13	26	+13	Sato 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

Code transparency0/20

Interface verifiability8/10

Docs & demo0/10

Listing transparency & provenance7/15

Independent verification3/10

The observed record

100% of 108 daily checks since 2026-07-14 succeeded. This is the share of OUR checks that succeeded. It is not uptime: a failed check can be on our side. When a check before 2026-09-01 failed, the checks before that date are left out of the rate: the probe counted a bot-block as a failure then and recorded no reason for any failure.

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.

Date	Score	Tier	Status	Our check
2026-10-29	38	Low	Active	up
2026-10-28	38	Low	Active	up
2026-10-27	38	Low	Active	up
2026-10-26	38	Low	Active	up
2026-10-25	38	Low	Active	up
2026-10-24	38	Low	Active	up
2026-10-23	38	Low	Active	up
2026-10-22	38	Low	Active	up
2026-10-21	38	Low	Active	up
2026-10-20	38	Low	Active	up
2026-10-19	38	Low	Active	up
2026-10-18	38	Low	Active	up
2026-10-17	38	Low	Active	up
2026-10-16	38	Low	Active	up
2026-10-15	38	Low	Active	up
2026-10-14	38	Low	Active	up
2026-10-13	38	Low	Active	up
2026-10-12	38	Low	Active	up
2026-10-11	38	Low	Active	up
2026-10-10	38	Low	Active	up
2026-10-09	38	Low	Active	up
2026-10-08	38	Low	Active	up
2026-10-07	38	Low	Active	up
2026-10-06	38	Low	Active	up
2026-10-05	38	Low	Active	up
2026-10-04	38	Low	Active	up
2026-10-03	38	Low	Active	up
2026-10-02	38	Low	Active	up
2026-10-01	38	Low	Active	up
2026-09-30	38	Low	Active	up
2026-09-29	38	Low	Active	up
2026-09-28	38	Low	Active	up
2026-09-27	38	Low	Active	up
2026-09-26	38	Low	Active	up
2026-09-25	38	Low	Active	up
2026-09-24	38	Low	Active	up
2026-09-23	38	Low	Active	up
2026-09-22	38	Low	Active	up
2026-09-21	30	Low	Active	up
2026-09-20	30	Low	Active	up
2026-09-19	30	Low	Active	up
2026-09-18	30	Low	Active	up
2026-09-17	30	Low	Active	up
2026-09-16	30	Low	Active	up
2026-09-15	30	Low	Active	up
2026-09-14	30	Low	Active	up
2026-09-13	30	Low	Active	up
2026-09-12	30	Low	Active	up
2026-09-11	30	Low	Active	up
2026-09-10	30	Low	Active	up
2026-09-09	30	Low	Active	up
2026-09-08	30	Low	Active	up
2026-09-07	30	Low	Active	up
2026-09-06	30	Low	Active	up
2026-09-05	30	Low	Active	up
2026-09-04	30	Low	Active	up
2026-09-03	30	Low	Active	up
2026-09-02	30	Low	Active	up
2026-09-01	30	Low	Active	up
2026-08-31	27	Low	Active	up
2026-08-30	27	Low	Active	up
2026-08-29	27	Low	Active	up
2026-08-28	27	Low	Active	up
2026-08-27	27	Low	Active	up
2026-08-26	27	Low	Active	up
2026-08-25	27	Low	Active	up
2026-08-24	27	Low	Active	up
2026-08-23	27	Low	Active	up
2026-08-22	27	Low	Active	up
2026-08-21	27	Low	Active	up
2026-08-20	27	Low	Active	up
2026-08-19	27	Low	Active	up
2026-08-18	27	Low	Active	up
2026-08-17	27	Low	Active	up
2026-08-16	27	Low	Active	up
2026-08-15	27	Low	Active	up
2026-08-14	27	Low	Active	up
2026-08-13	27	Low	Active	up
2026-08-12	27	Low	Active	up
2026-08-11	27	Low	Active	up
2026-08-10	27	Low	Active	up
2026-08-09	27	Low	Active	up
2026-08-08	27	Low	Active	up
2026-08-07	27	Low	Active	up
2026-08-06	27	Low	Active	up
2026-08-05	27	Low	Active	up
2026-08-04	27	Low	Active	up
2026-08-03	27	Low	Active	up
2026-08-02	27	Low	Active	up
2026-08-01	27	Low	Active	up
2026-07-31	27	Low	Active	up
2026-07-30	27	Low	Active	up
2026-07-29	27	Low	Active	up
2026-07-28	27	Low	Active	up
2026-07-27	27	Low	Active	up
2026-07-26	27	Low	Active	up
2026-07-25	27	Low	Active	up
2026-07-24	27	Low	Active	up
2026-07-23	27	Low	Active	up
2026-07-22	27	Low	Active	up
2026-07-21	27	Low	Active	up
2026-07-20	27	Low	Active	up
2026-07-19	26	Low	Active	up
2026-07-18	26	Low	Active	up
2026-07-17	26	Low	Active	up
2026-07-16	26	Low	Active	up
2026-07-15	26	Low	Active	up
2026-07-14	26	Low	Active	up
2026-07-13	13	Low	Active	not 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.

Sep 21, 2026
Verified: deploy spec
Aug 1, 2026
Sato Hub began tracking this listing
Jul 14, 2026
Enriched: tags
Jul 13, 2026
Listed on Sato Hub

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 record This week’s movers Dispute this score