Read 2026-10-04
casey/just: technical due diligence, read from its repository
What Borehole read in casey/just's code and history at 7aed5c9: 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
LICENSE.md: Relicensed: Apache-2.0 → CC0-1.0 (2017-11-30)
Architecture & Codebase — including AI provenance
strongsrc/parser.rs is 3,439 lines, 39× this codebase's median file
adequateThe median source file here is 88 lines. 6 files exceed 1,000 lines, the largest being 3,439. 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/parser.rs:1 — 3,439 lines (39× median) |
src/lexer.rs:1 — 2,546 lines (28× median) |
src/justfile.rs:1 — 1,480 lines (16× median) |
src/config.rs:1 — 1,325 lines (15× median) |
src/subcommand.rs:1 — 1,167 lines (13× 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 322 tracked files; 0 present |
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.
etc/Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate7 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/ci.yaml:30 — action pinned by tag |
.github/workflows/ci.yaml:55 — action pinned by tag |
Relicensed: Apache-2.0 → CC0-1.0 (2017-11-30)
adequateThe root licence changed 1 time(s). Code taken under earlier terms stays under them; check which terms any fork or customer relied on.
LICENSE.md — Apache-2.0 from 2016-11-13 |
LICENSE — CC0-1.0 from 2017-11-30 |
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 casey/just: 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.