Read 2026-10-23
openmeterio/openmeter: technical due diligence, read from its repository
What Borehole read in openmeterio/openmeter's code and history at f04b561: 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 | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | strong |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongapi/client/javascript/src/zod/index.ts is 20,250 lines, 189× this codebase's median file
adequateThe median source file here is 107 lines. 153 files exceed 1,070 lines, the largest being 20,250. 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.
api/client/javascript/src/zod/index.ts:1 — 20,250 lines (189× median) |
openmeter/ent/db/client.go:1 — 18,155 lines (169× median) |
openmeter/ent/db/setorclear.go:1 — 6,674 lines (62× median) |
openmeter/ent/db/migrate/schema.go:1 — 6,508 lines (60× median) |
openmeter/ent/db/paginate.go:1 — 5,173 lines (48× median) |
Engineering Process & SDLC Maturity
adequate12% of recent commits change more than 2,000 lines
adequate240 of 2028 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.
| 240 commits over 2,000 lines |
Product & Engineering Maturity
adequate94 direct dependencies in a single manifest
adequatego.mod declares 94 direct dependencies. Each one is a maintenance obligation, a supply-chain surface and a potential licence question that transfers with the asset. The count says nothing about whether any given dependency was a good choice; it says how many such choices a buyer inherits.
go.mod — 94 declared |
collector/go.mod — 21 declared |
api/client/python/pyproject.toml — 10 declared |
api/client/javascript/package.json — 2 declared |
Security & Reliability Posture
adequate2 credential-shaped strings committed to the tree
adequateMatches for JWT appear in tracked files outside test and fixture paths. They stay in the history even after they leave the tree, so what matters is whether each was rotated. This is significant because at least one sits in configuration a deployed system reads. Is any of these live? Show that each was rotated after it was committed, and when.
| JWT pattern matched, production configuration |
| JWT pattern matched |
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.
api/v3/client/transport.go:42 — outbound call without a timeout |
app/common/llmcost.go:44 — outbound call without a timeout |
2 of 3 Kubernetes workloads declare no resource limits
adequate2 workload manifests set no CPU or memory limits. One pod that leaks memory or spins can starve everything else on its node, and the scheduler cannot plan capacity for what it cannot see.
deploy/charts/openmeter/templates/deployment.yaml — workload with no limits |
deploy/charts/openmeter/templates/svix.yaml — workload with no limits |
1 locked dependency has published vulnerabilities, 1 high or critical
adequate1 of 899 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. None of the high or critical ones is in what the product ships: they are development dependencies.
api/client/javascript/pnpm-lock.yaml — zod 4.4.3: GHSA-mrhx-c7xc-m3w5 (high), fixed in 4.6.6; a development dependency |
2 advisories against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-08-04. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. Whether 1 of them are fixed in the code you ship could not be told from this history: its version is only known to be at least 0.2.0. Answer lives in: the release you run, set against each fixed version. GHSA-wc3v-3457-c8cm (moderate) is fixed in the surveyed commit; which release carries it cannot be told from this history, which does not place the release users run. Answer lives in: the version you run.
| 2026-08-04: GHSA-m2fw-9wxq-jgf5 (critical): SQL injection through customer usageAttribution subjectKeys (and key) into the shared ClickHouse meter/event query |
| 2026-05-19: GHSA-wc3v-3457-c8cm (moderate), fixed in 1.0.0-beta.228: OpenMeter: SQL injection through meter creation |
Observability & Operations
strongNo 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 openmeterio/openmeter: 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.