Borehole · Project · free tier
scottblodgett/voice-biomarker-poc
Free reading: not for reliance
ff6747e · 2 commits · 34 files
Read 2026-10-13

scottblodgett/voice-biomarker-poc: technical due diligence, read from its repository

What Borehole read in scottblodgett/voice-biomarker-poc's code and history at ff6747e: 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.

DimensionRating
Architecture & Codebase — including AI provenanceadequate
Engineering Process & SDLC Maturitynot assessable
Product & Engineering Maturitynot assessable
Security & Reliability Postureadequate
Observability & Operationsadequate
Fit with the Acquirernot assessable

What the repository says

  • README.md:104: This repository is a mirror; development happens elsewhere

Architecture & Codebase — including AI provenance

adequate
01.2

The repository begins with most of itself already written

adequate

The first commit carries 8,099 lines — 98% 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.

Evidence
2026-09-28T15:19:16+00:00; +8,099 across 33 files; subject: 'Voice biomarker POC: three AI systems over one recording, re'

Engineering Process & SDLC Maturity

not assessable
02.6

Almost no process scaffolding exists in the repository

adequate

Of 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.

Evidence
0 of 5 markers present across 34 tracked files

Product & Engineering Maturity

not assessable

Not rated: only 3 of 19 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.

Security & Reliability Posture

adequate
05.2

None of the standard security guard rails are configured

adequate

There 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.

Evidence
checked 5 kinds of guard rail across 34 tracked files; 0 present
05.26

3 locked dependencies have published vulnerabilities, 4 high or critical

adequate

3 of 45 locked dependencies match 9 published advisories in OSV, 4 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: their lockfile is a separate application (an internal tool, an editor extension), not the product.

Evidence
kintsugi-ui/package-lock.json — next 16.3.3: GHSA-vcvr-r3jv-pc5j (critical), fixed in 16.3.6; in a separate application's lockfile
kintsugi-ui/package-lock.json — sharp 0.35.4: GHSA-wq5f-xc86-pv6w (high), fixed in 0.35.5; in a separate application's lockfile
kintsugi-ui/package-lock.json — source-map-js 1.2.1: GHSA-68fv-2mgg-jv7q (high), fixed in 1.2.2; in a separate application's lockfile

Observability & Operations

adequate
06.1

No telemetry or error reporting is wired in anywhere

adequate

None of 23 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.

Evidence
searched 23 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
06.2

No structured logging library is in use

adequate

Nothing 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.

Evidence
searched 23 files for 10 structured logging libraries; 0 matched
06.8

One request cannot be followed through the logs

adequate

Nothing 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.

Evidence
no request id, correlation id or tracing found
06.9

No error reporter is wired in

adequate

Nothing 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.

Evidence
no error reporter initialised

Fit with the Acquirer

not assessable

Not rated: structurally not assessable from a repository.

Read more, or read your own

The full report on scottblodgett/voice-biomarker-poc: 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.