Java repositories

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.

All bands Strong Adequate 106 surveyed
Sort Relevance Newest Stars Lines of code Files History Findings Worst band
RepositoryLanguageSizeStarsReadBand
freeplane/freeplane 2 adequate · 2 strong Java 477,713 lines 4,433 2026-10-23 adequate
tduckcloud/tduck-survey-form 3 adequate · 1 strong Java 29,559 lines 1,258 2026-11-03 adequate
topiam/eiam 3 adequate · 2 strong Java 154,529 lines 1,219 2026-11-03 adequate
scouter-project/scouter 2 adequate · 1 strong Java 271,886 lines 2,179 2026-10-28 adequate
jobrunr/jobrunr 4 strong Java 90,753 lines 3,100 2026-10-23 strong
javamelody/javamelody 1 adequate · 2 strong Java 104,436 lines 3,043 2026-10-23 adequate
1panel-dev/cordyscrm 4 adequate · 1 strong Java 414,120 lines 2,808 2026-10-23 adequate
alfio-event/alf.io 4 adequate · 1 strong Java 236,828 lines 1,626 2026-10-28 adequate
pac4j/pac4j 1 adequate · 3 strong Java 117,467 lines 2,537 2026-10-23 strong
codeberg.org/freeyourgadget/gadgetbridge 3 adequate · 1 strong Java 880,449 lines 1,946 2026-10-25 adequate
vipshop/saturn 3 adequate · 2 strong Java 93,311 lines 2,306 2026-10-23 adequate
spiculedata/saiku 3 adequate · 2 strong Java 490,055 lines 1,334 2026-10-28 adequate
dromara/maxkey 4 adequate · 1 strong Java 220,697 lines 1,977 2026-10-23 adequate
zinggai/zingg 1 adequate · 3 strong Java 64,729 lines 1,261 2026-10-23 strong
dromara/skyeye 3 adequate · 1 strong Java 440,473 lines 1,234 2026-10-23 adequate
codeberg.org/gitnex/gitnex 2 adequate · 1 strong Java 82,315 lines 919 2026-10-25 adequate

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.