Read 2026-11-03
modem-dev/hunk: technical due diligence, read from its repository
What Borehole read in modem-dev/hunk's code and history at 544bc40: 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 | strong |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongpackages/hunk/src/app/cli.ts is 2,731 lines, 20× this codebase's median file
adequateThe median source file here is 135 lines. 9 files exceed 1,350 lines, the largest being 2,731. 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.
packages/hunk/src/app/cli.ts:1 — 2,731 lines (20× median) |
packages/hunk/src/ui/components/panes/DiffPane.tsx:1 — 2,695 lines (19× median) |
packages/hunk/src/extension-api/types.ts:1 — 2,658 lines (19× median) |
packages/hunk/src/ui/App.tsx:1 — 1,979 lines (14× median) |
packages/hunk/src/ui/hooks/useTerminalReview.ts:1 — 1,939 lines (14× median) |
Engineering Process & SDLC Maturity
adequateTests are retried until they pass
adequateThe suite is configured to retry failing tests (website/playwright.config.ts). A retry turns a flaky test green without saying why it failed, so a green build means the tests passed eventually. Ask how many retries a typical run needs, and which tests need them.
website/playwright.config.ts:8 — test retry |
7% of recent commits change more than 2,000 lines
adequate61 of 830 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.
| 61 commits over 2,000 lines |
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
strongThe build runs third-party code it does not pin
adequate4 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.
install.sh:10 — download piped into a shell |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 1,514 readable files references an instrumentation, metrics or error-reporting library. If this system is in production, nobody learns that it broke from the system itself — they learn it from a customer. That is a reliability finding before it is an observability one.
| searched 1,514 tracked text files for 16 known instrumentation libraries; manifests for metrics, tracing and error-reporting families; locked dependencies for the packages that emit; 0 matched |
No structured logging library is in use
adequateNothing references a structured logging library. Logs that are written to be read by a person are not searchable by a machine, which means incident response here is proportional to how well someone remembers the codebase rather than to what the tooling can find.
| searched 1,514 files for 10 structured logging libraries; 0 matched |
No error reporter is wired in
adequateNothing in the service initialises an error reporter (Sentry, Rollbar, Bugsnag, Honeybadger or an APM agent). An exception in production reaches a person only if someone is reading the logs, which usually means a customer reports it first.
| no error reporter initialised |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on modem-dev/hunk: 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.