Read 2026-10-23
future-architect/vuls: technical due diligence, read from its repository
What Borehole read in future-architect/vuls's code and history at 6e79331: 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 | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
LICENSE: Relicensed: GPL-3.0 → AGPL-3.0 (2019-09-09) → GPL-3.0 (2021-12-26).gitmodules:1: 1 submodule(s) this survey does not read: integration
Architecture & Codebase — including AI provenance
strongscanner/windows.go is 5,776 lines, 40× this codebase's median file
adequateThe median source file here is 143 lines. 4 files exceed 1,430 lines, the largest being 5,776. 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.
scanner/windows.go:1 — 5,776 lines (40× median) |
detector/vuls2/vuls2.go:1 — 2,351 lines (16× median) |
detector/vuls2/vendor.go:1 — 2,153 lines (15× median) |
scanner/base.go:1 — 1,567 lines (10× median) |
Engineering Process & SDLC Maturity
adequateAlmost 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 308 tracked files |
7% of recent commits change more than 2,000 lines
adequate12 of 171 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.
| 12 commits over 2,000 lines |
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequate1 credential-shaped string in the tree sit in tests, examples, documentation or local development settings
adequateStrings shaped like credentials appear only where fakes are usual: test fixtures, examples, documentation, placeholders and local stacks. They are almost always fakes. Ask someone to confirm that none of them works anywhere, because a real key in a development file is still a real key.
| Slack token, where fakes are usual |
1 Dockerfile runs the application as root
adequateNo USER instruction switches away from root, so the process runs with full privileges inside the container. It is a one-line fix and an ordinary expectation, which is why its absence is worth asking about: it usually says more about whether anyone has reviewed the deployment than about this container specifically.
Dockerfile — runs as root |
2 outbound calls can wait forever
adequate2 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.
reporter/http.go:27 — outbound call without a timeout |
util/util.go:194 — outbound call without a timeout |
12 SQL statements built from strings
adequate12 places in product code build SQL by formatting or joining strings rather than passing parameters. In each, what the code shows going in is a table or column name, a constant, or something the line does not show, not a request's value. Ask whether any value reaches these strings, rather than a parameter.
scanner/base.go:138 — SQL built from a string |
scanner/base.go:656 — SQL built from a string |
scanner/base.go:699 — SQL built from a string |
1 locked dependency has published vulnerabilities, 1 high or critical in what ships
adequate1 of 361 locked dependencies match 1 published advisories in OSV, 1 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.
go.mod — github.com/aquasecurity/trivy v0.74.0: GO-2026-4919 (critical) |
Relicensed: GPL-3.0 → AGPL-3.0 (2019-09-09) → GPL-3.0 (2021-12-26)
adequateThe root licence changed 2 time(s). Code taken under earlier terms stays under them; check which terms any fork or customer relied on.
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 |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on future-architect/vuls: 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.