Score history

aixbt

Name: aixbt — 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 136d

+20

Days measured

136

Days missed

Sato Score, daily

2026-06-11 → 2026-10-29

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, 3 caused by a revision of the scoring method.

Date	From	To	Change	Cause
2026-09-01	30	33	+3	Sato Hub changed the scoring method
2026-07-14	18	30	+12	Sato Hub changed the scoring method
2026-06-25	13	18	+5	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 & provenance10/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	33	Low	Active	up
2026-10-28	33	Low	Active	up
2026-10-27	33	Low	Active	up
2026-10-26	33	Low	Active	up
2026-10-25	33	Low	Active	up
2026-10-24	33	Low	Active	up
2026-10-23	33	Low	Active	up
2026-10-22	33	Low	Active	up
2026-10-21	33	Low	Active	up
2026-10-20	33	Low	Active	up
2026-10-19	33	Low	Active	up
2026-10-18	33	Low	Active	up
2026-10-17	33	Low	Active	up
2026-10-16	33	Low	Active	up
2026-10-15	33	Low	Active	up
2026-10-14	33	Low	Active	up
2026-10-13	33	Low	Active	up
2026-10-12	33	Low	Active	up
2026-10-11	33	Low	Active	up
2026-10-10	33	Low	Active	up
2026-10-09	33	Low	Active	up
2026-10-08	33	Low	Active	up
2026-10-07	33	Low	Active	up
2026-10-06	33	Low	Active	up
2026-10-05	33	Low	Active	up
2026-10-04	33	Low	Active	up
2026-10-03	33	Low	Active	up
2026-10-02	33	Low	Active	up
2026-10-01	33	Low	Active	up
2026-09-30	33	Low	Active	up
2026-09-29	33	Low	Active	up
2026-09-28	33	Low	Active	up
2026-09-27	33	Low	Active	up
2026-09-26	33	Low	Active	up
2026-09-25	33	Low	Active	up
2026-09-24	33	Low	Active	up
2026-09-23	33	Low	Active	up
2026-09-22	33	Low	Active	up
2026-09-21	33	Low	Active	up
2026-09-20	33	Low	Active	up
2026-09-19	33	Low	Active	up
2026-09-18	33	Low	Active	up
2026-09-17	33	Low	Active	up
2026-09-16	33	Low	Active	up
2026-09-15	33	Low	Active	up
2026-09-14	33	Low	Active	up
2026-09-13	33	Low	Active	up
2026-09-12	33	Low	Active	up
2026-09-11	33	Low	Active	up
2026-09-10	33	Low	Active	up
2026-09-09	33	Low	Active	up
2026-09-08	33	Low	Active	up
2026-09-07	33	Low	Active	up
2026-09-06	33	Low	Active	up
2026-09-05	33	Low	Active	up
2026-09-04	33	Low	Active	up
2026-09-03	33	Low	Active	up
2026-09-02	33	Low	Active	up
2026-09-01	33	Low	Active	up
2026-08-31	30	Low	Active	up
2026-08-30	30	Low	Active	up
2026-08-29	30	Low	Active	up
2026-08-28	30	Low	Active	up
2026-08-27	30	Low	Active	up
2026-08-26	30	Low	Active	up
2026-08-25	30	Low	Active	up
2026-08-24	30	Low	Active	up
2026-08-23	30	Low	Active	up
2026-08-22	30	Low	Active	up
2026-08-21	30	Low	Active	up
2026-08-20	30	Low	Active	up
2026-08-19	30	Low	Active	up
2026-08-18	30	Low	Active	up
2026-08-17	30	Low	Active	up
2026-08-16	30	Low	Active	up
2026-08-15	30	Low	Active	up
2026-08-14	30	Low	Active	up
2026-08-13	30	Low	Active	up
2026-08-12	30	Low	Active	up
2026-08-11	30	Low	Active	up
2026-08-10	30	Low	Active	up
2026-08-09	30	Low	Active	up
2026-08-08	30	Low	Active	up
2026-08-07	30	Low	Active	up
2026-08-06	30	Low	Active	up
2026-08-05	30	Low	Active	up
2026-08-04	30	Low	Active	up
2026-08-03	30	Low	Active	up
2026-08-02	30	Low	Active	up
2026-08-01	30	Low	Active	up
2026-07-31	30	Low	Active	up
2026-07-30	30	Low	Active	up
2026-07-29	30	Low	Active	up
2026-07-28	30	Low	Active	up
2026-07-27	30	Low	Active	up
2026-07-26	30	Low	Active	up
2026-07-25	30	Low	Active	up
2026-07-24	30	Low	Active	up
2026-07-23	30	Low	Active	up
2026-07-22	30	Low	Active	up
2026-07-21	30	Low	Active	up
2026-07-20	30	Low	Active	up
2026-07-19	30	Low	Active	up
2026-07-18	30	Low	Active	up
2026-07-17	30	Low	Active	up
2026-07-16	30	Low	Active	up
2026-07-15	30	Low	Active	up
2026-07-14	30	Low	Active	up
2026-07-13	18	Low	Active	not checked
2026-07-12	18	Low	Active	not checked
2026-07-11	18	Low	Active	not checked
2026-07-10	18	Low	Active	not checked
2026-07-09	18	Low	Active	not checked
2026-07-08	18	Low	Active	not checked
2026-07-07	18	Low	Active	not checked
2026-07-06	18	Low	Active	not checked
2026-07-05	18	Low	Active	not checked
2026-07-04	18	Low	Active	not checked
2026-07-03	18	Low	Active	not checked
2026-07-02	18	Low	Active	not checked
2026-07-01	18	Low	Active	not checked
2026-06-30	18	Low	Active	not checked
2026-06-27	18	Low	Active	not checked
2026-06-26	18	Low	Active	not checked
2026-06-25	18	Low	Active	not checked
2026-06-24	13	Low	Active	not checked
2026-06-22	13	Low	Active	not checked
2026-06-20	13	Low	Active	not checked
2026-06-19	13	Low	Active	not checked
2026-06-18	13	Low	Active	not checked
2026-06-17	13	Low	Active	not checked
2026-06-16	13	Low	Active	not checked
2026-06-15	13	Low	Active	not checked
2026-06-14	13	Low	Active	not checked
2026-06-13	13	Low	Active	not checked
2026-06-12	13	Low	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.

Aug 1, 2026
Sato Hub began tracking this listing
Jun 25, 2026
Enriched: supported integrations, deployment options, marketplace notes

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