Python 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.
| Repository | Language | Size | Stars | Read | Band |
|---|---|---|---|---|---|
| celery/kombu 4 strong | Python | 63,448 lines | 3,151 | 2026-10-23 | |
| pretix/pretix 3 adequate · 2 strong | Python | 454,829 lines | 2,529 | 2026-10-25 | |
| oauthlib/oauthlib 1 adequate · 3 strong | Python | 24,733 lines | 2,988 | 2026-10-23 | |
| dbos-inc/dbos-transact-py 4 strong | Python | 79,825 lines | 1,653 | 2026-10-28 | |
| outflanknl/redelk 1 adequate · 3 strong | Python | 40,656 lines | 2,684 | 2026-10-23 | |
| frappe/frappe_docker 2 adequate · 3 strong | Python | 10,623 lines | 2,604 | 2026-10-23 | |
| brightbeanxyz/brightbean-studio 3 adequate · 2 strong | Python | 160,211 lines | 2,563 | 2026-10-23 | |
| suitenumerique/meet 4 adequate · 1 strong | Python | 149,669 lines | 2,447 | 2026-10-23 | |
| django-crm/django-crm 3 adequate · 2 strong | Python | 518,381 lines | 2,459 | 2026-10-23 | |
| meltano/meltano 1 adequate · 3 strong | Python | 146,467 lines | 2,667 | 2026-10-22 | |
| gitguardian/ggshield 1 adequate · 3 strong | Python | 117,171 lines | 2,009 | 2026-10-23 | |
| tsingyuai/growth-lab 1 adequate · 2 strong | Python | 9,936 lines | 1,971 | 2026-10-23 | |
| uselotus/lotus 3 adequate · 2 strong | Python | 130,173 lines | 1,841 | 2026-10-23 | |
| dj-stripe/dj-stripe 4 strong | Python | 49,518 lines | 1,795 | 2026-10-23 | |
| django-helpdesk/django-helpdesk 2 adequate · 3 strong | Python | 40,714 lines | 1,692 | 2026-10-23 | |
| obsei/obsei 2 adequate · 3 strong | Python | 47,651 lines | 1,441 | 2026-10-23 | |
| baristaze/swe_guidelines 1 adequate · 4 strong | Python | 237,263 lines | 94 | 2026-10-25 | |
| baristaze/tadas 3 adequate · 2 strong | Python | 181,671 lines | 3 | 2026-10-05 | |
| scottblodgett/sweetwater 3 adequate · 1 strong | Python | 28,274 lines | — | 2026-10-13 | |
| jagusgelos/factored-hackathon-2026-jagusgelos 3 adequate · 2 strong | Python | 49,390 lines | — | 2026-10-12 | |
| yegamble/vidra 1 adequate · 3 strong | Python | 288,345 lines | — | 2026-10-08 | |
| markbgilbert/aegis-zero-gc-benchmark 2 adequate · 1 strong | Python | 4,337 lines | — | 2026-10-06 |
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.