Read 2026-10-28
harnessmd/munder-difflin: technical due diligence, read from its repository
What Borehole read in harnessmd/munder-difflin's code and history at f797048: 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
strongsrc/main/index.ts is 5,512 lines, 31× this codebase's median file
adequateThe median source file here is 177 lines. 4 files exceed 1,770 lines, the largest being 5,512. 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/main/index.ts:1 — 5,512 lines (31× median) |
src/main/hive.ts:1 — 3,670 lines (20× median) |
src/renderer/src/components/SettingsModal.tsx:1 — 2,122 lines (11× median) |
src/renderer/src/scene/office/OfficeFloor.tsx:1 — 1,806 lines (10× median) |
Engineering Process & SDLC Maturity
adequate8% of recent commits change more than 2,000 lines
adequate80 of 984 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.
| 80 commits over 2,000 lines |
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequate13 credential-shaped strings in the tree 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.
| 2 cited: GitHub token, where fakes are usual |
| 3 cited: Slack token, where fakes are usual |
25 locked dependencies have published vulnerabilities, 35 high or critical in what ships
adequate25 of 662 locked dependencies match 96 published advisories in OSV, 54 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.
package-lock.json — proxy-addr 2.0.7: GHSA-jqcg-44mw-7w3h (critical), fixed in 2.0.8 |
landing-remotion/package-lock.json — remotion 4.0.286: GHSA-2jqp-f4gr-44fr (critical), fixed in 4.0.410; in a separate application's lockfile |
package-lock.json — @modelcontextprotocol/sdk 1.29.0: GHSA-22jm-h49p-29qw (high), fixed in 1.32.0 |
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 harnessmd/munder-difflin: 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.