Read 2026-10-23
builderio/builder: technical due diligence, read from its repository
What Borehole read in builderio/builder's code and history at c4497e9: 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 | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongNo finding.
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequateFixes are 56% of recent work, up from 33%
adequateIn the last two quarters 56% of commits were fixes, against 33% in the quarters before. Rising fix work usually means quality debt is coming due, and it takes time that new work would have had.
| 63%, 50%, 42%, 38%, 38%, 20%, 27%, 33% |
Security & Reliability Posture
adequate1 environment file is committed
adequatepackages/sdks/snippets/hydrogen/.env is tracked in git. Environment files are where credentials usually live, and committing one usually means nobody decided how secrets reach the running application. Whatever is in it is in the history for good. Check 05.1 says whether it holds anything credential-shaped.
packages/sdks/snippets/hydrogen/.env — committed environment file |
The build runs third-party code it does not pin
adequate3 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/lint-and-commit.yml:50 — action pinned by tag |
.github/workflows/publish-sdks.yml:49 — action pinned by tag |
219 locked dependencies have published vulnerabilities, 27 high or critical in what ships
adequate219 of 7,554 locked dependencies match 380 published advisories in OSV, 179 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.
packages/shopify/package-lock.json — handlebars 4.7.7: GHSA-2w6w-674q-4c4q (critical), fixed in 4.7.9 |
packages/cli/package-lock.json — vm2 3.11.5: GHSA-27g9-p43v-cw3v (critical), fixed in 3.11.7 |
yarn.lock — @nuxt/devtools 1.7.0: GHSA-279x-mwfv-vcqv (critical), fixed in 3.3.1 |
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 builderio/builder: 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.