Ruby repositories reading adequate
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 |
|---|---|---|---|---|---|
| Featured: chosen by hand. | |||||
| chatwoot/chatwoot 3 adequate · 2 strong | Ruby | 1,283,524 lines | 37,217 | 2026-11-08 | |
| Every other reading, as the automated checks produced it. | |||||
| hashicorp/vagrant 3 strong | Ruby | 165,793 lines | 27,216 | 2026-11-07 | |
| gollum/gollum 1 adequate · 4 strong | Ruby | 13,050 lines | 14,334 | 2026-11-07 | |
| freecodecamp/devdocs 4 adequate · 1 strong | Ruby | 74,507 lines | 39,575 | 2026-10-28 | |
| jekyll/jekyll 3 strong | Ruby | 51,885 lines | 51,698 | 2026-10-25 | |
| discourse/discourse 2 adequate · 2 strong | Ruby | 2,225,419 lines | 47,898 | 2026-10-25 | |
| wpscanteam/wpscan 2 adequate · 2 strong | Ruby | 237,075 lines | 9,832 | 2026-11-03 | |
| activerecord-hackery/ransack 3 strong | Ruby | 25,013 lines | 5,858 | 2026-11-07 | |
| rmosolgo/graphql-ruby 2 adequate · 2 strong | Ruby | 491,573 lines | 5,445 | 2026-11-08 | |
| heartcombo/devise 3 strong | Ruby | 19,184 lines | 24,355 | 2026-10-25 | |
| rails/thor 3 strong | Ruby | 14,703 lines | 5,262 | 2026-11-07 | |
| docusealco/docuseal 3 adequate · 2 strong | Ruby | 127,325 lines | 18,639 | 2026-10-25 | |
| sinatra/sinatra 3 strong | Ruby | 30,701 lines | 12,453 | 2026-10-25 | |
| rubygems/rubygems.org 3 adequate · 2 strong | Ruby | 114,212 lines | 2,441 | 2026-11-08 | |
| omniauth/omniauth 1 adequate · 2 strong | Ruby | 8,251 lines | 8,106 | 2026-10-28 | |
| manyfold3d/manyfold 4 adequate · 1 strong | Ruby | 90,677 lines | 2,224 | 2026-11-03 | |
| zammad/zammad 3 adequate · 2 strong | Ruby | 1,134,488 lines | 5,972 | 2026-10-25 | |
| rack/rack 1 adequate · 2 strong | Ruby | 25,462 lines | 5,132 | 2026-10-25 | |
| sharetribe/sharetribe 3 adequate · 2 strong | Ruby | 412,940 lines | 2,448 | 2026-10-28 | |
| flippercloud/flipper 3 adequate · 2 strong | Ruby | 45,795 lines | 3,973 | 2026-10-23 | |
| multiwoven/multiwoven 3 adequate · 2 strong | Ruby | 84,771 lines | 1,683 | 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.