Read 2026-10-23
qwikdev/partytown: technical due diligence, read from its repository
What Borehole read in qwikdev/partytown's code and history at fd6cbb4: 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 | strong |
| 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
strongTests are retried until they pass
adequateThe suite is configured to retry failing tests (tests/integrations/intercom/vendor-modern.d054d6ff.js). 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.
tests/integrations/intercom/vendor-modern.d054d6ff.js:6697 — test retry |
Product & Engineering Maturity
strongNode.js 20 is past end of life
adequateThe code is pinned to Node.js 20 (end of life 2026-04-30). None of these receives security fixes any more; the first stopped on 2026-04-30. Moving off an unsupported runtime is rarely a one-line change, so a buyer should ask whether the upgrade is planned and what it touches.
.nvmrc — Node.js 20, end of life 2026-04-30 |
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 510 tracked files; 0 present |
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/ci.yml:12 — action pinned by tag |
.github/workflows/pr.yml:20 — action pinned by tag |
3 locked dependencies have published vulnerabilities, 2 high or critical
adequate3 of 485 locked dependencies match 4 published advisories in OSV, 2 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. None of the high or critical ones is in what the product ships: they are development dependencies.
pnpm-lock.yaml — shell-quote 1.9.0: GHSA-pqg4-j6r4-53mv (critical), fixed in 1.11.0; a development dependency |
pnpm-lock.yaml — tmp 0.0.33: GHSA-ph9p-34f9-6g65 (high), fixed in 0.2.6; a development dependency |
pnpm-lock.yaml — esbuild 0.15.18: GHSA-67mh-4wv8-2f99 (moderate), fixed in 0.25.0; a development dependency |
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 qwikdev/partytown: 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.