Read 2026-11-03
aboutcode-org/scancode-toolkit: technical due diligence, read from its repository
What Borehole read in aboutcode-org/scancode-toolkit's code and history at e423b48: 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 |
Architecture & Codebase — including AI provenance
strongsrc/cluecode/copyrights.py is 4,735 lines, 338× this codebase's median file
adequateThe median source file here is 14 lines. 17 files exceed 1,000 lines, the largest being 4,735. 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.
src/cluecode/copyrights.py:1 — 4,735 lines (338× median) |
src/licensedcode/legalese.py:1 — 4,578 lines (327× median) |
src/licensedcode/match.py:1 — 3,393 lines (242× median) |
src/licensedcode/models.py:1 — 3,079 lines (219× median) |
src/packagedcode/pypi.py:1 — 2,958 lines (211× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongNo finding.
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 65,427 tracked files; 0 present |
1 credential-shaped string added in the history sit in tests, examples, documentation or local development settings
adequateStrings shaped like credentials appear only where fakes are usual: test fixtures, examples, documentation, placeholders and local stacks. They are almost always fakes. Ask someone to confirm that none of them works anywhere, because a real key in a development file is still a real key.
| Google API key, where fakes are usual |
1 Dockerfile runs the application as root
adequateNo USER instruction switches away from root, so the process runs with full privileges inside the container. It is a one-line fix and an ordinary expectation, which is why its absence is worth asking about: it usually says more about whether anyone has reviewed the deployment than about this container specifically.
Dockerfile — runs as root |
3 deserialisers that can run code
adequate3 places read data with a deserialiser that executes what it reads (pickle). That is safe on data the system wrote itself and remote code execution on anything else. Ask where each one's input comes from.
src/licensedcode/cache.py:445 — code-executing deserialiser |
src/packagedcode/cache.py:256 — code-executing deserialiser |
src/textcode/gibberish.py:39 — code-executing deserialiser |
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 aboutcode-org/scancode-toolkit: 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.