Sato Hub
Score history

Laso Finance

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

Score today

35

Change over 48d

-25

Days measured

48

Days missed

0

Sato Score, daily

2026-09-23 → 2026-11-09
02550751002026-09-23: 60 (Medium)2026-09-24: 60 (Medium)2026-09-25: 62 (Medium)2026-09-26: 62 (Medium)2026-09-27: 35 (Low)2026-09-28: 35 (Low)2026-09-29: 35 (Low)2026-09-30: 35 (Low)2026-10-01: 35 (Low)2026-10-02: 35 (Low)2026-10-03: 35 (Low)2026-10-04: 35 (Low)2026-10-05: 35 (Low)2026-10-06: 35 (Low)2026-10-07: 35 (Low)2026-10-08: 35 (Low)2026-10-09: 35 (Low)2026-10-10: 35 (Low)2026-10-11: 35 (Low)2026-10-12: 35 (Low)2026-10-13: 35 (Low)2026-10-14: 35 (Low)2026-10-15: 35 (Low)2026-10-16: 35 (Low)2026-10-17: 35 (Low)2026-10-18: 35 (Low)2026-10-19: 35 (Low)2026-10-20: 35 (Low)2026-10-21: 35 (Low)2026-10-22: 35 (Low)2026-10-23: 35 (Low)2026-10-24: 35 (Low)2026-10-25: 35 (Low)2026-10-26: 35 (Low)2026-10-27: 35 (Low)2026-10-28: 35 (Low)2026-10-29: 35 (Low)2026-10-30: 35 (Low)2026-10-31: 35 (Low)2026-11-01: 35 (Low)2026-11-02: 35 (Low)2026-11-03: 35 (Low)2026-11-04: 35 (Low)2026-11-05: 35 (Low)2026-11-06: 35 (Low)2026-11-07: 35 (Low)2026-11-08: 35 (Low)2026-11-09: 35 (Low)6062352026-09-232026-11-09

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

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

DateFromToChangeCause
2026-09-276235-27the project
2026-09-256062+2the 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.

Maintenance & liveness8/35
35
Code transparency0/20
20
Interface verifiability10/10
10
Docs & demo6/10
10
Listing transparency & provenance7/15
15
Independent verification4/10
10

The observed record

8.3% of 48 daily checks since 2026-09-23 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.

2026-09-23: answered our check2026-09-24: answered our check2026-09-25: answered our check2026-09-26: answered our check2026-09-27: failed on our side — not attributable to the project2026-09-28: failed on our side — not attributable to the project2026-09-29: failed on our side — not attributable to the project2026-09-30: failed on our side — not attributable to the project2026-10-01: failed on our side — not attributable to the project2026-10-02: failed on our side — not attributable to the project2026-10-03: failed on our side — not attributable to the project2026-10-04: failed on our side — not attributable to the project2026-10-05: failed on our side — not attributable to the project2026-10-06: failed on our side — not attributable to the project2026-10-07: failed on our side — not attributable to the project2026-10-08: failed on our side — not attributable to the project2026-10-09: failed on our side — not attributable to the project2026-10-10: failed on our side — not attributable to the project2026-10-11: failed on our side — not attributable to the project2026-10-12: failed on our side — not attributable to the project2026-10-13: failed on our side — not attributable to the project2026-10-14: failed on our side — not attributable to the project2026-10-15: failed on our side — not attributable to the project2026-10-16: failed on our side — not attributable to the project2026-10-17: failed on our side — not attributable to the project2026-10-18: failed on our side — not attributable to the project2026-10-19: failed on our side — not attributable to the project2026-10-20: failed on our side — not attributable to the project2026-10-21: failed on our side — not attributable to the project2026-10-22: failed on our side — not attributable to the project2026-10-23: failed on our side — not attributable to the project2026-10-24: failed on our side — not attributable to the project2026-10-25: failed on our side — not attributable to the project2026-10-26: failed on our side — not attributable to the project2026-10-27: failed on our side — not attributable to the project2026-10-28: failed on our side — not attributable to the project2026-10-29: failed on our side — not attributable to the project2026-10-30: failed on our side — not attributable to the project2026-10-31: failed on our side — not attributable to the project2026-11-01: failed on our side — not attributable to the project2026-11-02: failed on our side — not attributable to the project2026-11-03: failed on our side — not attributable to the project2026-11-04: failed on our side — not attributable to the project2026-11-05: failed on our side — not attributable to the project2026-11-06: failed on our side — not attributable to the project2026-11-07: failed on our side — not attributable to the project2026-11-08: failed on our side — not attributable to the project2026-11-09: failed on our side — not attributable to the project
  • 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.

DateScoreTierStatusOur check
2026-11-0935LowActiveinconclusive
2026-11-0835LowActiveinconclusive
2026-11-0735LowActiveinconclusive
2026-11-0635LowActiveinconclusive
2026-11-0535LowActiveinconclusive
2026-11-0435LowActiveinconclusive
2026-11-0335LowActiveinconclusive
2026-11-0235LowActiveinconclusive
2026-11-0135LowActiveinconclusive
2026-10-3135LowActiveinconclusive
2026-10-3035LowActiveinconclusive
2026-10-2935LowActiveinconclusive
2026-10-2835LowActiveinconclusive
2026-10-2735LowActiveinconclusive
2026-10-2635LowActiveinconclusive
2026-10-2535LowActiveinconclusive
2026-10-2435LowActiveinconclusive
2026-10-2335LowActiveinconclusive
2026-10-2235LowActiveinconclusive
2026-10-2135LowActiveinconclusive
2026-10-2035LowActiveinconclusive
2026-10-1935LowActiveinconclusive
2026-10-1835LowActiveinconclusive
2026-10-1735LowActiveinconclusive
2026-10-1635LowActiveinconclusive
2026-10-1535LowActiveinconclusive
2026-10-1435LowActiveinconclusive
2026-10-1335LowActiveinconclusive
2026-10-1235LowActiveinconclusive
2026-10-1135LowActiveinconclusive
2026-10-1035LowActiveinconclusive
2026-10-0935LowActiveinconclusive
2026-10-0835LowActiveinconclusive
2026-10-0735LowActiveinconclusive
2026-10-0635LowActiveinconclusive
2026-10-0535LowActiveinconclusive
2026-10-0435LowActiveinconclusive
2026-10-0335LowActiveinconclusive
2026-10-0235LowActiveinconclusive
2026-10-0135LowActiveinconclusive
2026-09-3035LowActiveinconclusive
2026-09-2935LowActiveinconclusive
2026-09-2835LowActiveinconclusive
2026-09-2735LowActiveinconclusive
2026-09-2662MediumActiveup
2026-09-2562MediumActiveup
2026-09-2460MediumActiveup
2026-09-2360MediumActiveup

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.

  1. Sep 27, 2026
    Sato Score tier: Medium → Low
    Score 62 → 35.
  2. Sep 25, 2026
    Auto-enriched: supported integrations
  3. Sep 23, 2026
    Listed on Sato Hub
  4. Sep 23, 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 recordThis week’s moversDispute this score