Read 2026-11-03
ossf/cve-bin-tool: technical due diligence, read from its repository
What Borehole read in ossf/cve-bin-tool's code and history at 4bfd4d3: 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 | adequate |
| Product & Engineering Maturity | adequate |
| Security & Reliability Posture | strong |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
- No release for 17 months while development continues
Architecture & Codebase — including AI provenance
strongcve_bin_tool/cli.py is 1,367 lines, 48× this codebase's median file
adequateThe median source file here is 28 lines. 3 files exceed 1,000 lines, the largest being 1,367. 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.
cve_bin_tool/cli.py:1 — 1,367 lines (48× median) |
cve_bin_tool/cvedb.py:1 — 1,205 lines (43× median) |
cve_bin_tool/output_engine/__init__.py:1 — 1,010 lines (36× median) |
Engineering Process & SDLC Maturity
adequatePinned dependencies have not moved in 27 months
adequateThe lockfile last changed 816 days before the newest commit, and 1,225 commits have landed since. Every security fix published upstream in that time is absent until someone updates it, and the longer the gap the larger and riskier that update becomes.
| test/language_data/Cargo.lock last changed 2024-08-08 |
Product & Engineering Maturity
adequateNo release for 17 months while development continues
adequateThe last tag, v3.4.1rc0, was cut 510 days before the survey; the typical gap between releases was 12 days, and 110 commits landed in the last 90 days. Users run the last release, not this code.
| last tag v3.4.1rc0 |
Security & Reliability Posture
strongThe build runs third-party code it does not pin
adequate3 third-party CI actions are referenced by a tag or branch rather than a commit, so they run whatever that tag points to on the day. Tags have been moved to malicious commits in real supply-chain attacks, and a piped script is whatever the server returns that minute. Pinning to a commit is the fix, and it is small.
.github/workflows/cve_bin_tool_action.yml:17 — action pinned by tag |
.github/workflows/spelling.yml:30 — action pinned by tag |
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 ossf/cve-bin-tool: 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.