Read 2026-10-23
evidence-dev/evidence: technical due diligence, read from its repository
What Borehole read in evidence-dev/evidence's code and history at 505913c: 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
AGENTS.md:5: This repository is a mirror; development happens elsewhere- Releases are cut from another branch than the one surveyed
Architecture & Codebase — including AI provenance
strongcore/src/user-components/common/pivot-utils.ts is 2,611 lines, 46× this codebase's median file
adequateThe median source file here is 56 lines. 11 files exceed 1,000 lines, the largest being 2,611. 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.
core/src/user-components/common/pivot-utils.ts:1 — 2,611 lines (46× median) |
cli/cli/migrate/transform.ts:1 — 2,482 lines (44× median) |
core/src/user-components/Renderer/MarkdocProcessor/process-markdoc.ts:1 — 1,630 lines (29× median) |
core/src/user-components/tags/table/Table.svelte:1 — 1,523 lines (27× median) |
core/src/user-components/common/build-comparisons.ts:1 — 1,385 lines (24× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest release, v2.2.1, is not on the branch this survey read. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v2.2.1 |
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 2,129 tracked files; 0 present |
The build runs third-party code it does not pin
adequate2 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; 2 steps pipe a download straight into a shell. 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/cli-build.yml:17 — action pinned by tag |
.github/workflows/cli-build.yml:26 — action pinned by tag |
cli/scripts/install.sh:3 — download piped into a shell |
24 locked dependencies have published vulnerabilities, 18 high or critical in what ships
adequate24 of 1,015 locked dependencies match 68 published advisories in OSV, 27 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.
pnpm-lock.yaml — dompurify 3.4.13: GHSA-cg2g-xh64-v4q7 (critical), fixed in 3.4.17 |
pnpm-lock.yaml — axios 1.19.0: GHSA-3pq3-5fj3-cg6v (high), fixed in 1.20.0 |
pnpm-lock.yaml — basic-ftp 5.3.1: GHSA-c475-qrg2-pj4r (high), fixed in 6.2.1 |
21 places insert HTML from a variable without sanitising it
adequate21 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.
cli/src/routes/+layout.svelte:168 — HTML from a variable |
cli/src/routes/+page.svelte:44 — HTML from a variable |
cli/src/routes/+page.svelte:49 — HTML from a variable |
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,593 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 evidence-dev/evidence: 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.