Read 2026-10-04
unkeyed/unkey: technical due diligence, read from its repository
What Borehole read in unkeyed/unkey's code and history at 837586e: 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 | strong |
| Fit with the Acquirer | not assessable |
What the repository says
LICENSE: Relicensed: GPL-3.0 → AGPL-3.0 (2024-02-05)
Architecture & Codebase — including AI provenance
strongsvc/api/openapi/gen.go is 7,773 lines, 127× this codebase's median file
adequateThe median source file here is 61 lines. 11 files exceed 1,000 lines, the largest being 7,773. 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.
svc/api/openapi/gen.go:1 — 7,773 lines (127× median) |
pkg/db/querier_generated.go:1 — 3,678 lines (60× median) |
svc/ctrl/internal/db/querier_generated.go:1 — 2,468 lines (40× median) |
internal/services/ratelimit/db/models_generated.go:1 — 1,788 lines (29× median) |
web/apps/dashboard/app/api/webhooks/stripe/route.ts:1 — 1,384 lines (22× median) |
Engineering Process & SDLC Maturity
adequate8% of recent commits change more than 2,000 lines
adequate228 of 2755 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.
| 228 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.
| JWT, where fakes are usual |
9 outbound calls can wait forever
adequate9 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.
cmd/healthcheck/main.go:44 — outbound call without a timeout |
pkg/circuitbreaker/doc.go:26 — outbound call without a timeout |
pkg/retry/retry.go:39 — outbound call without a timeout |
1 SQL statement built from strings
adequate1 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.
pkg/clickhouse/flush.go:26 — SQL built from a string |
61 locked dependencies have published vulnerabilities, 38 high or critical in what ships
adequate61 of 2,384 locked dependencies match 147 published advisories in OSV, 67 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. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.
go.mod — google.golang.org/grpc v1.78.0: GHSA-p77j-4mvh-x3m3 (critical), fixed in 1.79.3 |
go.mod — github.com/jackc/pgx/v5 v5.7.5: GHSA-9jj7-4m8r-rfcm (critical), fixed in 5.9.0 |
web/pnpm-lock.yaml — astro 7.1.6: GHSA-26w7-cxv4-gfx2 (critical), fixed in 7.2.8; reached only by the build |
The production build publishes source maps
adequateThe build configuration emits source maps for production, so the original source, with its comments and structure, is downloadable by every visitor. Upload them to an error tracker and keep them off the public server instead.
web/apps/dashboard/next.config.js:131 — source maps in a production build |
Relicensed: GPL-3.0 → AGPL-3.0 (2024-02-05)
adequateThe root licence changed 1 time(s). The latest terms restrict what users, hosts or a buyer may do in ways the earlier ones did not. Code taken under the old terms stays under them, so both matter in diligence.
Observability & Operations
strongThe code branches on the environment's name at 15 places
adequate15 places outside configuration test whether they are running in production or staging. Staging then does not exercise production's code, and each deploy is the first run of those branches. Differences belong in configuration the code reads, not in the code.
gen/proto/hydra/v1/github_status.pb.go:103 — branch on the environment name |
gen/proto/hydra/v1/github_status.pb.go:103 — branch on the environment name |
gen/proto/hydra/v1/github_status.pb.go:103 — branch on the environment name |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on unkeyed/unkey: 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.