Read 2026-10-28
open-telemetry/opentelemetry-go: technical due diligence, read from its repository
What Borehole read in open-telemetry/opentelemetry-go's code and history at 57d5430: 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 | strong |
| Product & Engineering Maturity | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
CONTRIBUTING.md:13: names CNCFREADME.md:6: names OpenSSF
Architecture & Codebase — including AI provenance
strongsemconv/v1.43.0/k8sconv/metric.go is 20,783 lines, 146× this codebase's median file
adequateThe median source file here is 142 lines. 137 files exceed 1,420 lines, the largest being 20,783. 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.
semconv/v1.43.0/k8sconv/metric.go:1 — 20,783 lines (146× median) |
semconv/v1.42.0/k8sconv/metric.go:1 — 20,764 lines (146× median) |
semconv/v1.41.0/k8sconv/metric.go:1 — 20,564 lines (144× median) |
semconv/v1.41.0/attribute_group.go:1 — 17,290 lines (121× median) |
semconv/v1.40.0/attribute_group.go:1 — 16,866 lines (118× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequate10 credential-shaped strings 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.
| 5 cited: private key block, where fakes are usual |
11 advisories against this project in the last 24 months, 3 high or critical
adequateThe newest was published on 2026-09-02. 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.
| 2026-09-02: GHSA-8wmf-6v46-5gfg (low), fixed in >= 1.45.0: Exporter config logging may leak endpoint URLs in info logs |
| 2026-09-02: GHSA-p9f8-wvj8-2fg8 (moderate), fixed in >= v1.33.0: UTF-8 replacement rune bypasses attribute length truncation |
| 2026-09-02: GHSA-hjf4-fphr-2h65 (moderate), fixed in v0.21.0: BatchProcessor can busy-spin when export buffer is full |
| 2026-09-02: GHSA-w34q-cm8f-9c5x (moderate), fixed in >= v0.21.0: Log gRPC exporter ignores env TLS certs, bypassing mTLS/pinning |
| 2026-08-20: GHSA-42cj-99w8-cp2p (moderate), fixed in >= v1.45.0: Unsynchronized baggage map can panic under concurrent access |
Observability & Operations
not assessableNot rated: only 5 of 16 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on open-telemetry/opentelemetry-go: 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.