Read 2026-10-04
koalaman/shellcheck: technical due diligence, read from its repository
What Borehole read in koalaman/shellcheck's code and history at 5fe4d42: 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 | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
LICENSE: Relicensed: AGPL-3.0 → GPL-3.0 (2015-06-20)
Architecture & Codebase — including AI provenance
strongsrc/ShellCheck/Analytics.hs is 5,274 lines, 20× this codebase's median file
adequateThe median source file here is 261 lines. 2 files exceed 2,610 lines, the largest being 5,274. 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/ShellCheck/Analytics.hs:1 — 5,274 lines (20× median) |
src/ShellCheck/Parser.hs:1 — 3,673 lines (14× median) |
Engineering Process & SDLC Maturity
strongAlmost no process scaffolding exists in the repository
adequateOf five ordinary markers — CI workflows, CODEOWNERS, a pull-request template, pre-commit hooks, contribution guidance — 1 is present: CI workflows. Branch protection itself is a GitHub setting rather than a file, so this is a reading of proxies and not of the rules themselves. What it does establish is that the process is not written down anywhere a new engineer would find it.
| 1 of 5 markers present across 91 tracked files |
Product & Engineering Maturity
adequateChange keeps returning to the same few files
adequateFive files out of 239 absorb 43% 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.
ShellCheck/Analytics.hs — 428 commits touched it |
src/ShellCheck/Analytics.hs — 320 commits touched it |
ShellCheck/Parser.hs — 272 commits touched it |
src/ShellCheck/Parser.hs — 138 commits touched it |
src/ShellCheck/AnalyzerLib.hs — 119 commits touched it |
Security & Reliability Posture
adequate7 Dockerfiles run 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.
builders/darwin.aarch64/Dockerfile — runs as root |
builders/darwin.x86_64/Dockerfile — runs as root |
builders/linux.aarch64/Dockerfile — runs as root |
builders/linux.armv6hf/Dockerfile — runs as root |
Observability & Operations
not assessableNot rated: only 4 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 koalaman/shellcheck: 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.