Score history

Brickken

Name: Brickken — 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 103d

+20

Days measured

103

Days missed

Sato Score, daily

2026-07-19 → 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

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

Date	From	To	Change	Cause
2026-10-23	28	32	+4	the project
2026-10-10	25	28	+3	Sato Hub changed the scoring method
2026-10-03	29	25	-4	the project
2026-09-03	25	29	+4	the project
2026-09-01	13	25	+12	Sato Hub changed the scoring method
2026-07-20	12	13	+1	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 verifiability0/10

Docs & demo0/10

Listing transparency & provenance5/15

Independent verification7/10

The observed record

100% of 59 daily checks since 2026-09-01 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	32	Low	Active	up
2026-10-28	32	Low	Active	up
2026-10-27	32	Low	Active	up
2026-10-26	32	Low	Active	up
2026-10-25	32	Low	Active	up
2026-10-24	32	Low	Active	up
2026-10-23	32	Low	Active	up
2026-10-22	28	Low	Active	up
2026-10-21	28	Low	Active	up
2026-10-20	28	Low	Active	up
2026-10-19	28	Low	Active	up
2026-10-18	28	Low	Active	up
2026-10-17	28	Low	Active	up
2026-10-16	28	Low	Active	up
2026-10-15	28	Low	Active	up
2026-10-14	28	Low	Active	up
2026-10-13	28	Low	Active	up
2026-10-12	28	Low	Active	up
2026-10-11	28	Low	Active	up
2026-10-10	28	Low	Active	up
2026-10-09	25	Low	Active	up
2026-10-08	25	Low	Active	up
2026-10-07	25	Low	Active	up
2026-10-06	25	Low	Active	up
2026-10-05	25	Low	Active	up
2026-10-04	25	Low	Active	up
2026-10-03	25	Low	Active	up
2026-10-02	29	Low	Active	up
2026-10-01	29	Low	Active	up
2026-09-30	29	Low	Active	up
2026-09-29	29	Low	Active	up
2026-09-28	29	Low	Active	up
2026-09-27	29	Low	Active	up
2026-09-26	29	Low	Active	up
2026-09-25	29	Low	Active	up
2026-09-24	29	Low	Active	up
2026-09-23	29	Low	Active	up
2026-09-22	29	Low	Active	up
2026-09-21	29	Low	Active	up
2026-09-20	29	Low	Active	up
2026-09-19	29	Low	Active	up
2026-09-18	29	Low	Active	up
2026-09-17	29	Low	Active	up
2026-09-16	29	Low	Active	up
2026-09-15	29	Low	Active	up
2026-09-14	29	Low	Active	up
2026-09-13	29	Low	Active	up
2026-09-12	29	Low	Active	up
2026-09-11	29	Low	Active	up
2026-09-10	29	Low	Active	up
2026-09-09	29	Low	Active	up
2026-09-08	29	Low	Active	up
2026-09-07	29	Low	Active	up
2026-09-06	29	Low	Active	up
2026-09-05	29	Low	Active	up
2026-09-04	29	Low	Active	up
2026-09-03	29	Low	Active	up
2026-09-02	25	Low	Active	up
2026-09-01	25	Low	Active	up
2026-08-31	13	Low	Active	unknown
2026-08-30	13	Low	Active	unknown
2026-08-29	13	Low	Active	unknown
2026-08-28	13	Low	Active	unknown
2026-08-27	13	Low	Active	unknown
2026-08-26	13	Low	Active	unknown
2026-08-25	13	Low	Active	unknown
2026-08-24	13	Low	Active	unknown
2026-08-23	13	Low	Active	unknown
2026-08-22	13	Low	Active	unknown
2026-08-21	13	Low	Active	unknown
2026-08-20	13	Low	Active	unknown
2026-08-19	13	Low	Active	unknown
2026-08-18	13	Low	Active	unknown
2026-08-17	13	Low	Active	unknown
2026-08-16	13	Low	Active	unknown
2026-08-15	13	Low	Active	unknown
2026-08-14	13	Low	Active	unknown
2026-08-13	13	Low	Active	unknown
2026-08-12	13	Low	Active	unknown
2026-08-11	13	Low	Active	unknown
2026-08-10	13	Low	Active	unknown
2026-08-09	13	Low	Active	unknown
2026-08-08	13	Low	Active	unknown
2026-08-07	13	Low	Active	unknown
2026-08-06	13	Low	Active	unknown
2026-08-05	13	Low	Active	unknown
2026-08-04	13	Low	Active	unknown
2026-08-03	13	Low	Active	unknown
2026-08-02	13	Low	Active	unknown
2026-08-01	13	Low	Active	unknown
2026-07-31	13	Low	Active	unknown
2026-07-30	13	Low	Active	unknown
2026-07-29	13	Low	Active	unknown
2026-07-28	13	Low	Active	unknown
2026-07-27	13	Low	Active	unknown
2026-07-26	13	Low	Active	unknown
2026-07-25	13	Low	Active	unknown
2026-07-24	13	Low	Active	unknown
2026-07-23	13	Low	Active	unknown
2026-07-22	13	Low	Active	unknown
2026-07-21	13	Low	Active	unknown
2026-07-20	13	Low	Active	unknown
2026-07-19	12	Low	Active	unknown

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 26, 2026
Edited: entity class, resource type
Aug 1, 2026
Sato Hub began tracking this listing
Jul 21, 2026
Edited: onchain address
Jul 20, 2026
Edited: deploy spec
Jul 19, 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