Read 2026-10-28
wpengine/faustjs: technical due diligence, read from its repository
What Borehole read in wpengine/faustjs's code and history at 38c6876: 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 | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
Architecture & Codebase — including AI provenance
strongNo finding.
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongEffort is shifting from building to rewriting
adequateDeleted lines per line added rose from 0.64 to 1.39 between the first and second halves of this history. Rework is normal and often healthy, but a rising ratio means an increasing share of the team's time is spent replacing code that already exists rather than building what does not. Whether that is deliberate repayment or churn is a question for the team.
| first half 0.64, second half 1.39 (split 2023-11-07) |
Releases are cut from another branch than the one surveyed
adequateThe newest release, v0.0.0, is not on the branch this survey read. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v0.0.0 |
Security & Reliability Posture
adequate1 locked dependency has published vulnerabilities
adequate1 of 573 locked dependencies match 1 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.
package-lock.json — deepmerge 4.3.1: GHSA-gcqx-w48m-w2h4 (low) |
13 places insert HTML from a variable without sanitising it
adequate13 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.
packages/blocks/src/blocks/CoreCode.tsx:33 — HTML from a variable |
packages/blocks/src/blocks/CoreColumn.tsx:124 — HTML from a variable |
packages/blocks/src/blocks/CoreList.tsx:79 — HTML from a variable |
Licence text does not match a standard licence
adequateLICENSE exists but its text does not match any standard licence. A bespoke or hand-edited licence is not wrong, but it cannot be cleared by recognising its name: counsel has to read it, and until they do neither side knows precisely what rights transfer with the code.
LICENSE:1 — 1 lines, unrecognised |
2 advisories against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-07-06. 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. Answer lives in: the release you run, set against each fixed version.
| 2026-07-06: GHSA-398q-73w6-v5gj (moderate), fixed in 1.8.12: FaustWP local login bypasses WordPress authenticate callbacks |
| 2026-06-04: GHSA-q6pm-r77q-qcv3 (high), fixed in 1.8.11: FaustWP through 1.8.0 — Authentication Bypass via Initialization Vector Modification in Token Envelope |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 500 readable files references an instrumentation, metrics or error-reporting library. If this system is in production, nobody learns that it broke from the system itself — they learn it from a customer. That is a reliability finding before it is an observability one.
| searched 500 tracked text files for 16 known instrumentation libraries; manifests for metrics, tracing and error-reporting families; locked dependencies for the packages that emit; 0 matched |
No 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 500 files for 10 structured logging libraries; 0 matched |
One request cannot be followed through the logs
adequateNothing in the service carries a request or correlation id, and there is no tracing. When a customer reports a failure, the log lines that belong to their request cannot be picked out from everyone else's.
| no request id, correlation id or tracing found |
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 wpengine/faustjs: 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.