Read 2026-11-03
vinceanalytics/vince: technical due diligence, read from its repository
What Borehole read in vinceanalytics/vince's code and history at fc06f7a: 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 | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
assets/js/dashboard/extra/COPYING.txt: Part of the code is under a separate licence: assets/js/dashboard/extra/
Architecture & Codebase — including AI provenance
adequateThe repository begins with most of itself already written
adequateThe first commit carries 38,143 lines — 96% 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.
| 2024-11-19T13:56:18+00:00; +38,143 across 1620 files; subject: 'v1.8.0' |
internal/ua2/ua_client.go is 1,386 lines, 1386× this codebase's median file
adequateThe median source file here is 1 lines. 1 file exceed 1,000 lines, the largest being 1,386. 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.
internal/ua2/ua_client.go:1 — 1,386 lines (1386× median) |
1,027 errors caught and discarded in product code
adequate1,027 places catch an error and do nothing with it, across 1,027 files (37.7 per thousand lines). Each is a failure the system will not report. They surface later as problems nobody can explain, and they are cheap to fix now.
app/js/script.compat.exclusions.file-downloads.hash.js:1 — error caught and discarded |
app/js/script.compat.exclusions.file-downloads.hash.local.js:1 — error caught and discarded |
app/js/script.compat.exclusions.file-downloads.hash.local.manual.js:1 — error caught and discarded |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate23 test files against 1,235 source files (1.9%). 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.
| 23 test files / 1,235 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 — 1 is present: CI workflows. 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.
| 1 of 5 markers present across 1,610 tracked files |
Tests are retried until they pass
adequateThe suite is configured to retry failing tests (tracker/test/support/playwright.config.js). 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.
tracker/test/support/playwright.config.js:13 — test retry |
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 1,610 tracked files; 0 present |
The build runs third-party code it does not pin
adequate3 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. 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/release.yml:27 — action pinned by tag |
.github/workflows/release.yml:29 — action pinned by tag |
3 outbound calls can wait forever
adequate3 HTTP calls use a client with no timeout (Python `requests` without `timeout=`, or Go's default client). When a dependency slows down, each one holds a worker until the connection gives up, and enough of them take the service down with the dependency.
internal/geo/gen/main.go:45 — outbound call without a timeout |
internal/geo/gen/main.go:52 — outbound call without a timeout |
internal/location/gen/main.go:268 — outbound call without a timeout |
21 locked dependencies have published vulnerabilities, 12 high or critical in what ships
adequate21 of 302 locked dependencies match 55 published advisories in OSV, 28 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.
tracker/package-lock.json — handlebars 4.7.8: GHSA-2w6w-674q-4c4q (critical), fixed in 4.7.9 |
tracker/package-lock.json — proxy-addr 2.0.7: GHSA-jqcg-44mw-7w3h (critical), fixed in 2.0.8 |
tracker/package-lock.json — body-parser 1.20.1: GHSA-27r3-jxmh-p828 (high), fixed in 1.20.9 |
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.
app/public/js/app.js:5 — HTML from a variable |
app/public/js/app.js:6 — HTML from a variable |
app/public/js/app.js:6 — HTML from a variable |
Part of the code is under a separate licence: assets/js/dashboard/extra/
adequateA directory named for a paid edition carries its own licence. That code is usually not open source even where the rest is; what the buyer may do with each part differs.
assets/js/dashboard/extra/COPYING.txt — licence: unrecognised |
Observability & Operations
adequateOne 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 |
Readiness and liveness probes are identical in 1 of 1 workloads
adequateBoth probes call the same endpoint. When a dependency slows down, the liveness probe fails with the readiness probe, so the platform restarts pods that only needed taking out of rotation, and a partial outage becomes a full one. Liveness should ask whether the process is alive; readiness whether it can serve.
k8s/values.yaml — same probe endpoint twice |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on vinceanalytics/vince: 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.