Read 2026-10-28
bagisto/nextjs-commerce: technical due diligence, read from its repository
What Borehole read in bagisto/nextjs-commerce's code and history at 6cd5acd: 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 | not assessable |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
adequateThe repository begins with most of itself already written
adequateThe first commit carries 141,253 lines — 42% 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.
| 2022-02-16T09:29:04+00:00; +141,253 across 1270 files; subject: 'Initial commit' |
src/utils/bagisto/index.ts is 1,192 lines, 29× this codebase's median file
adequateThe median source file here is 40 lines. 1 file exceed 1,000 lines, the largest being 1,192. 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/utils/bagisto/index.ts:1 — 1,192 lines (29× median) |
Engineering Process & SDLC Maturity
adequateTests are absent or token
adequate0 test files against 374 source files (0.0%). This does not measure whether the tests are good, only whether enough of them exist for the codebase to be changed safely by someone who did not write it — which is exactly the situation after an acquisition.
| 0 test files / 374 source files |
Almost no process scaffolding exists in the repository
adequateOf five ordinary markers — CI workflows, CODEOWNERS, a pull-request template, pre-commit hooks, contribution guidance — none are present. Branch protection itself is a GitHub setting rather than a file, so this is a reading of proxies and not of the rules themselves. What it does establish is that the process is not written down anywhere a new engineer would find it.
| 0 of 5 markers present across 414 tracked files |
Product & Engineering Maturity
strongNo finding.
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 414 tracked files; 0 present |
4 locked dependencies have published vulnerabilities, 7 high or critical in what ships
adequate4 of 323 locked dependencies match 14 published advisories in OSV, 7 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 — next 16.3.4: GHSA-2464-fhr4-w9xw (critical), fixed in 16.4.1 |
package-lock.json — sharp 0.35.4: GHSA-wq5f-xc86-pv6w (high), fixed in 0.35.5 |
package-lock.json — source-map-js 1.2.1: GHSA-68fv-2mgg-jv7q (high), fixed in 1.2.2 |
9 places insert HTML from a variable without sanitising it
adequate9 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/app/(public)/account/orders/view/[orderId]/page.tsx:43 — HTML from a variable |
src/app/(public)/product/[...urlProduct]/page.tsx:222 — HTML from a variable |
src/components/customer-detail/compare/CompareTable.tsx:54 — HTML from a variable |
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 bagisto/nextjs-commerce: 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.