Borehole · Project · free tier
vouch/vouch-proxy
Free reading: not for reliance
75741a1 · 989 commits · 145 files
Read 2026-11-03

vouch/vouch-proxy: technical due diligence, read from its repository

What Borehole read in vouch/vouch-proxy's code and history at 75741a1: 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 provenancestrong
Engineering Process & SDLC Maturitystrong
Product & Engineering Maturitystrong
Security & Reliability Posturestrong
Observability & Operationsadequate
Fit with the Acquirernot assessable

Architecture & Codebase — including AI provenance

strong

No finding.

Engineering Process & SDLC Maturity

strong

No finding.

Product & Engineering Maturity

strong
04.1

Change keeps returning to the same few files

adequate

Five files out of 221 absorb 32% of all file-level change. Concentration like this is where debt is usually being serviced rather than repaid: the same code is reopened because it is load-bearing, fragile, or both. A repository cannot tell you which — that is a conversation with the team.

Evidence
README.md — 147 commits touched it
pkg/cfg/cfg.go — 143 commits touched it
handlers/handlers.go — 132 commits touched it
do.sh — 69 commits touched it
config/config.yml_example — 63 commits touched it

Security & Reliability Posture

strong
05.27

The build runs third-party code it does not pin

adequate

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

Evidence
.github/workflows/coverage.yml:37 — action pinned by tag
.github/workflows/docker-release-arm.yml:18 — action pinned by tag
05.13

4 outbound calls can wait forever

adequate

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

Evidence
pkg/healthcheck/healthcheck.go:46 — outbound call without a timeout
pkg/healthcheck/healthcheck.go:47 — outbound call without a timeout
pkg/providers/adfs/adfs.go:72 — outbound call without a timeout
05.65

1 advisory against this project in the last 24 months, 1 high or critical

adequate

The newest was published on 2026-06-11. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. None of them affects the surveyed version.

Evidence
2026-06-11: GHSA-qqff-5854-px68 (high), fixed in 0.48.0: vouch-proxy has an Unbounded Multipart Cookie Allocation DoS

Observability & Operations

adequate
06.1

No telemetry or error reporting is wired in anywhere

adequate

None of 112 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 112 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.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 vouch/vouch-proxy: 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.