Read 2026-10-08
sev7enup/nodepilot: technical due diligence, read from its repository
What Borehole read in sev7enup/nodepilot's code and history at 756e026: 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 | adequate |
| Engineering Process & SDLC Maturity | adequate |
| Product & Engineering Maturity | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | strong |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
adequateThe repository begins with most of itself already written
adequateThe first commit carries 412,735 lines — 57% of every line ever added. Whatever happened before that commit happened somewhere this repository cannot show you, so the early history is not available as evidence of how the system was designed.
| 2026-07-21T19:25:03+00:00; +412,735 across 2007 files; subject: 'NodePilot 1.0.0' |
deploy/Test-DeploymentTemplates.ps1 is 2,743 lines, 22× this codebase's median file
adequateThe median source file here is 123 lines. 16 files exceed 1,230 lines, the largest being 2,743. 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.
deploy/Test-DeploymentTemplates.ps1:1 — 2,743 lines (22× median) |
deploy/Preflight.ps1:1 — 2,101 lines (17× median) |
src/nodepilot-ui/src/pages/WorkflowEditorPage.tsx:1 — 2,015 lines (16× median) |
deploy/server/NodePilotServer.iss:1 — 2,002 lines (16× median) |
deploy/Install-NodePilot.ps1:1 — 1,858 lines (15× median) |
Engineering Process & SDLC Maturity
adequateTests are retried until they pass
adequateThe suite is configured to retry failing tests (src/nodepilot-ui/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.
src/nodepilot-ui/playwright.config.ts:22 — test retry |
6% of recent commits change more than 2,000 lines
adequate32 of 549 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.
| 32 commits over 2,000 lines |
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequate5 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.
| AWS access key, where fakes are usual |
| GitHub token, where fakes are usual |
| Slack token, where fakes are usual |
| 2 cited: JWT, where fakes are usual |
1 locked dependency has published vulnerabilities
adequate1 of 317 locked dependencies match 2 published advisories in OSV. 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.
src/nodepilot-ui/package-lock.json — dompurify 3.4.13: GHSA-6688-9rhm-gjv2 (low), fixed in 3.4.16 |
5 places insert HTML from a variable without sanitising it
adequate5 places set HTML from a value that is neither a literal nor passed through a sanitiser. Where the value can come from a user, that is stored cross-site scripting, and it is the first thing a buyer's security review looks for in a frontend.
src/nodepilot-docs-ui/src/site/experience/controller.ts:7 — HTML from a variable |
src/nodepilot-docs-ui/src/site/i18n/index.ts:77 — HTML from a variable |
src/nodepilot-docs-ui/src/site/main.ts:115 — HTML from a variable |
Observability & Operations
strongNo 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 sev7enup/nodepilot: 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.