Siebly Hyperliquid JavaScript SDK
One dated Sato Score reading per day. Days we changed the scoring method are marked. Not a safety or returns grade.
Score today
68
Change over 3d
+4
Days measured
3
Days missed
0
Sato Score, daily
2026-11-12 → 2026-11-14Every 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, 0 caused by a revision of the scoring method.
| Date | From | To | Change | Cause |
|---|---|---|---|---|
| 2026-11-13 | 64 | 68 | +4 | the project |
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.
The observed record
3 checks recorded, 3 in the rate window — too few to state a rate. 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-11-14 | 68 | Medium | Early | up |
| 2026-11-13 | 68 | Medium | Early | up |
| 2026-11-12 | 64 | Medium | Early | up |
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.
- Nov 13, 2026Auto-enriched: tags, creator name
- Nov 12, 2026Listed on Sato Hub
- Nov 12, 2026Sato Hub began tracking this listing
- Nov 12, 2026Updated: description long
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.