Read 2026-11-03
sonicjs-org/sonicjs: technical due diligence, read from its repository
What Borehole read in sonicjs-org/sonicjs's code and history at cb7e36f: 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 | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongpackages/core/src/templates/components/dynamic-field.template.ts is 2,690 lines, 22× this codebase's median file
adequateThe median source file here is 119 lines. 10 files exceed 1,190 lines, the largest being 2,690. 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.
packages/core/src/templates/components/dynamic-field.template.ts:1 — 2,690 lines (22× median) |
packages/core/src/routes/admin-content.ts:1 — 2,565 lines (21× median) |
packages/core/src/templates/pages/admin-plugin-settings.template.ts:1 — 1,679 lines (14× median) |
packages/core/src/routes/admin-users.ts:1 — 1,543 lines (12× median) |
packages/core/src/routes/auth.ts:1 — 1,526 lines (12× median) |
Engineering Process & SDLC Maturity
adequate72 tests are switched off
adequate72 skip markers across 40 of 366 test files. Each is a failure somebody chose to stop seeing; the question is whether anyone is tracking them.
packages/core/src/__tests__/middleware/logging.test.ts:23 — skipped test |
packages/core/src/__tests__/middleware/logging.test.ts:141 — skipped test |
packages/core/src/__tests__/middleware/logging.test.ts:216 — skipped test |
Tests are retried until they pass
adequateThe suite is configured to retry failing tests (tests/playwright.www.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.
tests/playwright.www.config.ts:24 — test retry |
6% of recent commits change more than 2,000 lines
adequate80 of 1384 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
adequateNode.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.
www/.node-version — Node.js 20, end of life 2026-04-30 |
API v3 and v1 have been served together for 41 months
adequatev1 first appeared in Jun 2023, and v3 is still in the code 41 months later. Two versions mean two surfaces to secure, document and support. Ask who still calls the old one, and whether retiring it is planned.
server/modules/contact-us/services/main.js — v3 since Nov 2019 |
src/server.ts — v1 since Jun 2023 |
Security & Reliability Posture
adequate46 locked dependencies have published vulnerabilities, 15 high or critical in what ships
adequate46 of 1,268 locked dependencies match 155 published advisories in OSV, 58 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 — proxy-addr 2.0.7: GHSA-jqcg-44mw-7w3h (critical), fixed in 2.0.8 |
my-sonicjs-app/pnpm-lock.yaml — shell-quote 1.8.3: GHSA-w7jw-789q-3m8p (critical), fixed in 1.8.4; a development dependency |
47 places insert HTML from a variable without sanitising it
adequate47 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.
my-sonicjs-app/src/plugins/qr-generator/templates/qr-form.template.ts:669 — HTML from a variable |
packages/core/src/plugins/core-plugins/_shared/quill-shared.ts:262 — HTML from a variable |
packages/core/src/plugins/core-plugins/_shared/tinymce-shared.ts:96 — HTML from a variable |
1 advisory against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-10-30. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. Whether 1 of them are fixed in the code you ship could not be told from this history: its version is only known to be at least 3.0.0. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 2 records name sonicjs with nothing tying them to this repository (CVE-2022-42002, CVE-2023-33690).
| 2026-10-30: CVE-2026-119707 (high): SonicJS through 3.0.0 contains a missing authorization vulnerability in the /api/:collection and /api/content write routes that only check coarse role labels. A |
Observability & Operations
adequateNo structured logging library is in use
adequateNothing references a structured logging library. Logs that are written to be read by a person are not searchable by a machine, which means incident response here is proportional to how well someone remembers the codebase rather than to what the tooling can find.
| searched 1,347 files for 10 structured logging libraries; 0 matched |
No 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 sonicjs-org/sonicjs: 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.