Java 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 |
|---|---|---|---|---|---|
| jabref/jabref 4 strong | Java | 493,723 lines | 4,777 | 2026-10-25 | |
| opendatadiscovery/odd-platform 1 adequate · 3 strong | Java | 205,132 lines | 1,441 | 2026-11-03 | |
| fasterxml/jackson-databind 4 strong | Java | 329,032 lines | 3,752 | 2026-10-25 | |
| jobrunr/jobrunr 4 strong | Java | 90,753 lines | 3,100 | 2026-10-23 | |
| pac4j/pac4j 1 adequate · 3 strong | Java | 117,467 lines | 2,537 | 2026-10-23 | |
| zinggai/zingg 1 adequate · 3 strong | Java | 64,729 lines | 1,261 | 2026-10-23 |
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.