Scala repositories reading strong
Every public repository surveyed, browsable and searchable. Including the unflattering ones — a tool that only published good results would be a badge vending machine, not a diligence instrument.
| Repository | Language | Size | Stars | Read | Band |
|---|---|---|---|---|---|
| delta-io/delta 2 adequate · 3 strong | Scala | 697,961 lines | 9,066 | 2026-11-03 | |
| scala-js/scala-js 1 adequate · 3 strong | Scala | 320,692 lines | 4,707 | 2026-11-07 | |
| gatling/gatling 1 adequate · 3 strong | Scala | 117,321 lines | 6,957 | 2026-11-03 | |
| lichess-org/lila 2 adequate · 3 strong | Scala | 304,839 lines | 18,773 | 2026-10-25 | |
| akka/akka-core 5 strong | Scala | 854,694 lines | 13,281 | 2026-10-25 | |
| playframework/playframework 2 adequate · 3 strong | Scala | 265,998 lines | 12,615 | 2026-10-25 | |
| typelevel/skunk 1 adequate · 4 strong | Scala | 32,054 lines | 1,667 | 2026-11-07 | |
| acinq/eclair 1 adequate · 4 strong | Scala | 169,740 lines | 1,349 | 2026-11-03 |
What a band means. A band sums up one reading of one commit: strong, adequate or significant findings. Here it counts the project's code, process, product, security and operations. A report reads more than that, so its band can differ from its row.
How listing works. Every public repository surveyed is listed — assessing public work is commentary on public work, and a library that hid the small ones would be quietly editorialising about which code counts. Private repositories are never listed. Anyone who proves control of a repo can attach a response to a finding, request a re-run, or delist it. Delisting is immediate and no-questions. An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev. There is no org-level score. Repositories are listed one by one, and sorting by band orders them by their own readings. Takedown: one email, 48 hours.