Score history

dYdX

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

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

Change over 90d

Days measured

Days missed

Sato Score, daily

2026-06-11 → 2026-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, 2 caused by a revision of the scoring method.

Date	From	To	Change	Cause
2026-08-27	73	83	+10	the project
2026-08-23	83	73	-10	the project
2026-07-14	90	83	-7	Sato Hub changed the scoring method
2026-06-25	82	90	+8	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 & liveness35/35

Code transparency19/20

Interface verifiability0/10

Docs & demo6/10

Listing transparency & provenance15/15

Independent verification8/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.

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-09-13	83	High	Active	up
2026-09-12	83	High	Active	up
2026-09-11	83	High	Active	up
2026-09-10	83	High	Active	up
2026-09-09	83	High	Active	up
2026-09-08	83	High	Active	up
2026-09-07	83	High	Active	up
2026-09-06	83	High	Active	up
2026-09-05	83	High	Active	up
2026-09-04	83	High	Active	up
2026-09-03	83	High	Active	up
2026-09-02	83	High	Active	up
2026-09-01	83	High	Active	up
2026-08-31	83	High	Active	up
2026-08-30	83	High	Active	up
2026-08-29	83	High	Active	up
2026-08-28	83	High	Active	up
2026-08-27	83	High	Active	up
2026-08-26	73	High	Active	up
2026-08-25	73	High	Active	up
2026-08-24	73	High	Active	up
2026-08-23	73	High	Active	up
2026-08-22	83	High	Active	up
2026-08-21	83	High	Active	up
2026-08-20	83	High	Active	up
2026-08-19	83	High	Active	up
2026-08-18	83	High	Active	up
2026-08-17	83	High	Active	up
2026-08-16	83	High	Active	up
2026-08-15	83	High	Active	up
2026-08-14	83	High	Active	up
2026-08-13	83	High	Active	up
2026-08-12	83	High	Active	up
2026-08-11	83	High	Active	up
2026-08-10	83	High	Active	up
2026-08-09	83	High	Active	up
2026-08-08	83	High	Active	up
2026-08-07	83	High	Active	up
2026-08-06	83	High	Active	up
2026-08-05	83	High	Active	up
2026-08-04	83	High	Active	up
2026-08-03	83	High	Active	up
2026-08-02	83	High	Active	up
2026-08-01	83	High	Active	up
2026-07-31	83	High	Active	up
2026-07-30	83	High	Active	up
2026-07-29	83	High	Active	up
2026-07-28	83	High	Active	up
2026-07-27	83	High	Active	up
2026-07-26	83	High	Active	up
2026-07-25	83	High	Active	up
2026-07-24	83	High	Active	up
2026-07-23	83	High	Active	up
2026-07-22	83	High	Active	up
2026-07-21	83	High	Active	up
2026-07-20	83	High	Active	up
2026-07-19	83	High	Active	up
2026-07-18	83	High	Active	up
2026-07-17	83	High	Active	up
2026-07-16	83	High	Active	up
2026-07-15	83	High	Active	up
2026-07-14	83	High	Active	up
2026-07-13	90	High	Active	not checked
2026-07-12	90	High	Active	not checked
2026-07-11	90	High	Active	not checked
2026-07-10	90	High	Active	not checked
2026-07-09	90	High	Active	not checked
2026-07-08	90	High	Active	not checked
2026-07-07	90	High	Active	not checked
2026-07-06	90	High	Active	not checked
2026-07-05	90	High	Active	not checked
2026-07-04	90	High	Active	not checked
2026-07-03	90	High	Active	not checked
2026-07-02	90	High	Active	not checked
2026-07-01	90	High	Active	not checked
2026-06-30	90	High	Active	not checked
2026-06-27	90	High	Active	not checked
2026-06-26	90	High	Active	not checked
2026-06-25	90	High	Active	not checked
2026-06-24	82	High	Active	not checked
2026-06-22	82	High	Active	not checked
2026-06-20	82	High	Active	not checked
2026-06-19	82	High	Active	not checked
2026-06-18	82	High	Active	not checked
2026-06-17	82	High	Active	not checked
2026-06-16	82	High	Active	not checked
2026-06-15	82	High	Active	not checked
2026-06-14	82	High	Active	not checked
2026-06-13	82	High	Active	not checked
2026-06-12	82	High	Active	not checked
2026-06-11	unknown	—	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 6, 2026
New release published
Sep 5, 2026
New release published
Aug 26, 2026
4 releases tracked
Showing the 2 most recent. Full release history is retained in the listing record.
Jul 14, 2026
Edited: deploy spec
Jun 25, 2026
Enriched: marketplace notes
Jun 25, 2026
Auto-enriched: creator profile url, creator name, deployment options, supported integrations +2 more
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 record This week’s movers Dispute this score