Read 2026-10-23
apache/casbin: technical due diligence, read from its repository
What Borehole read in apache/casbin's code and history at c35c93d: its licence, security advisories, releases, review practice, tests, dependencies and operations. Every finding cites the file and line it rests on. The full report also covers the team and asks the questions the code cannot answer.
| Dimension | Rating |
|---|---|
| Architecture & Codebase — including AI provenance | strong |
| Engineering Process & SDLC Maturity | strong |
| Product & Engineering Maturity | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
README.md:2: names Apache Software FoundationREADME.md:28: names OpenSSF
Architecture & Codebase — including AI provenance
strongrbac/default-role-manager/role_manager.go is 1,397 lines, 10× this codebase's median file
adequateThe median source file here is 135 lines. 1 file exceed 1,350 lines, the largest being 1,397. Size is not a defect on its own — some problems genuinely live in one place — but these are where merge conflicts, review fatigue and single-owner knowledge concentrate, and they are the first thing that slows an inheriting engineer down.
rbac/default-role-manager/role_manager.go:1 — 1,397 lines (10× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongChange keeps returning to the same few files
adequateFive files out of 448 absorb 26% of all file-level change. Concentration like this is where debt is usually being serviced rather than repaid: the same code is reopened because it is load-bearing, fragile, or both. A repository cannot tell you which — that is a conversation with the team.
README.md — 235 commits touched it |
enforcer.go — 223 commits touched it |
enforcer_test.go — 101 commits touched it |
model_test.go — 74 commits touched it |
rbac_api.go — 70 commits touched it |
Security & Reliability Posture
adequateNone of the standard security guard rails are configured
adequateThere is no disclosure policy, no automated dependency updates, no named code owners and no pre-commit configuration. None of these is load-bearing on its own. Their collective absence says that security posture here is whatever the current team happens to remember to do, which is not a posture that survives the team changing.
| checked 5 kinds of guard rail across 326 tracked files; 0 present |
Observability & Operations
not assessableNot rated: only 5 of 16 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on apache/casbin: every dimension, the questions for the room, and the audit log.
Survey a repository: free on public repositories. Private code is read on your own machine by a collector whose source you can read first.