Read 2026-10-28
moonrepo/moon: technical due diligence, read from its repository
What Borehole read in moonrepo/moon's code and history at 8b7db6b: 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 | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongcrates/action-graph/src/action_graph_builder.rs is 2,290 lines, 26× this codebase's median file
adequateThe median source file here is 85 lines. 8 files exceed 1,000 lines, the largest being 2,290. 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.
crates/action-graph/src/action_graph_builder.rs:1 — 2,290 lines (26× median) |
crates/action-pipeline/src/job_dispatcher.rs:1 — 1,784 lines (20× median) |
packages/types/src/workspace-config.ts:1 — 1,463 lines (17× median) |
crates/workspace/src/workspace_builder.rs:1 — 1,382 lines (16× median) |
crates/task-builder/src/tasks_builder.rs:1 — 1,372 lines (16× median) |
Engineering Process & SDLC Maturity
adequate9% of recent commits change more than 2,000 lines
adequate47 of 513 commits in the last 24 months changed over 2,000 lines of code, not counting reformatting, renames, vendored or generated code. A change that size is rarely reviewed line by line. Ask how they were reviewed, and what made them that large.
| 47 commits over 2,000 lines |
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 2,418 tracked files; 0 present |
The build runs third-party code it does not pin
adequate15 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; 3 steps pipe a download straight into a shell. 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/benchmark.yml:56 — action pinned by tag |
.github/workflows/benchmark.yml:62 — action pinned by tag |
.github/workflows/release.yml:73 — download piped into a shell |
53 locked dependencies have published vulnerabilities, 72 high or critical
adequate53 of 2,839 locked dependencies match 139 published advisories in OSV, 72 of them rated high or critical. A lockfile says which version is installed, not whether the flawed code is reachable from this product, so each needs a look. Most are fixed by an upgrade, and the advisory names the version. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.
The production build publishes source maps
adequateThe build configuration emits source maps for production, so the original source, with its comments and structure, is downloadable by every visitor. Upload them to an error tracker and keep them off the public server instead.
vite.config.ts:102 — source maps in a production build |
3 vendored components with no licence
adequateThird-party code is committed into this repository without any statement of the terms it arrived under. Unknown terms are harder to deal with than inconvenient ones: an awkward licence can be complied with, an absent one cannot. Each of these needs its origin established before the code changes hands.
crates/daemon-proto/vendor/README.md — 1 tracked files, no licence file |
crates/daemon-proto/vendor/google-api — 7 tracked files, no licence file |
crates/daemon-proto/vendor/remote-api — 2 tracked files, no licence file |
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 moonrepo/moon: 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.