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
debezium/debezium 2 adequate · 2 strong Java 642,270 lines 13,266 2026-10-23 adequate
starrocks/starrocks 4 strong Java 1,865,332 lines 12,202 2026-10-23 strong
apache/gravitino 1 adequate · 4 strong Java 1,399,544 lines 3,344 2026-11-03 strong
apereo/cas 1 adequate · 3 strong Java 886,239 lines 11,389 2026-10-23 strong
automq/automq 3 adequate · 2 strong Java 1,666,101 lines 10,922 2026-10-23 adequate
hapifhir/hapi-fhir 1 adequate · 3 strong Java 1,853,437 lines 2,427 2026-11-05 strong
obsidiandynamics/kafdrop 2 adequate · 2 strong Java 10,891 lines 6,156 2026-10-28 adequate
graylog2/graylog2-server 2 adequate · 3 strong Java 1,250,523 lines 8,151 2026-10-25 strong
strimzi/strimzi-kafka-operator 3 adequate · 2 strong Java 521,445 lines 5,964 2026-10-28 adequate
antennapod/antennapod 2 adequate · 2 strong Java 88,268 lines 8,182 2026-10-25 adequate
traccar/traccar 2 adequate · 3 strong Java 149,694 lines 7,822 2026-10-25 strong
flowable/flowable-engine 3 adequate · 2 strong Java 1,372,820 lines 9,616 2026-10-23 adequate
etar-group/etar-calendar 1 adequate · 2 strong Java 78,151 lines 2,631 2026-11-03 adequate
peergos/peergos 2 adequate · 1 strong Java 201,099 lines 2,548 2026-11-03 adequate
apache/shenyu 2 adequate · 3 strong Java 586,130 lines 8,903 2026-10-23 strong
iflytek/astron-agent 3 adequate · 2 strong Java 627,055 lines 8,916 2026-10-23 adequate
jooq/jooq 2 adequate · 2 strong Java 770,578 lines 6,793 2026-10-25 adequate
apache/hertzbeat 3 adequate · 2 strong Java 1,360,656 lines 7,437 2026-10-23 adequate
gocd/gocd 2 adequate · 3 strong Java 688,552 lines 7,432 2026-10-23 strong
eclipse-openvsx/openvsx 3 adequate · 2 strong Java 234,517 lines 2,067 2026-11-03 adequate
openremote/core 3 adequate · 2 strong Java 374,038 lines 1,970 2026-11-03 adequate
dromara/jpom 5 adequate Java 182,826 lines 1,951 2026-11-03 adequate
apache/flink-cdc 3 adequate · 1 strong Java 462,721 lines 6,485 2026-10-23 adequate
aklivity/zilla 3 adequate · 2 strong Java 1,247,467 lines 1,689 2026-11-03 adequate
jabref/jabref 4 strong Java 493,723 lines 4,777 2026-10-25 strong
killbill/killbill 1 adequate · 2 strong Java 299,381 lines 5,815 2026-10-23 adequate
datavane/tis 5 adequate Java 372,808 lines 1,440 2026-11-03 adequate
opendatadiscovery/odd-platform 1 adequate · 3 strong Java 205,132 lines 1,441 2026-11-03 strong
dtstack/taier 4 adequate · 1 strong Java 390,484 lines 1,287 2026-11-03 adequate
fasterxml/jackson-databind 4 strong Java 329,032 lines 3,752 2026-10-25 strong

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.