open-telemetry/opentelemetry-go

Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.

34 of your 74 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 2.85s · analysis 10.41s · 27.0 MB · GitHub API rate-limit (preflight)

https://github.com/open-telemetry/opentelemetry-go · scanned 2026-06-05 17:26 UTC (4 days, 22 hours ago) · 10 languages

330 raw signals (70 security + 260 graph) 11/13 scanners ran 70th percentile · Go · huge (>500K LoC) System graph score 82 (higher by 4)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 22 hours ago · v2 · 139 actionable findings from 2 signal sources. 59 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 130 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	85.0	0.15	12.75
`security_score`	100.0	0.25	25.00
`testing_score`	80.0	0.20	16.00
`documentation_score`	91.0	0.15	13.65
`practices_score`	93.0	0.15	13.95
`code_quality`	50.0	0.10	5.00
Overall		1.00	86.3

security_score may be inflated — optional security scanners were skipped on this fast scan

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 6 High 0 Medium 4 Low 122 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 9 System graph 130 Crowd 0 Layer: Quality 126 Software 2 Api 1 Network 1 Frontend 1 Security 6 Cicd 2

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Config drift 4 findings

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

4 matching findings on this repo

critical Insecure pattern 'private_key_in_repo' in exporters/otlp/otlptrace/otlptracegrp… exporters/otlp/otlptrace/otlptracegrpc/internal/o…:36
critical Insecure pattern 'private_key_in_repo' in exporters/otlp/otlptrace/otlptracehtt… exporters/otlp/otlptrace/otlptracehttp/internal/o…:36
critical Insecure pattern 'private_key_in_repo' in exporters/otlp/otlplog/otlploghttp/co… exporters/otlp/otlplog/otlploghttp/config_test.go:38
critical Insecure pattern 'private_key_in_repo' in exporters/otlp/otlplog/otlploggrpc/co… exporters/otlp/otlplog/otlploggrpc/config_test.go:38

View all config drift findings →

For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.

For AI agents + API integrations

Email me when this repo regresses

Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.

API access

This page is publicly accessible at: https://repobility.com/scan/9e627ed6-31e8-4ed0-a807-8aa24a1a7af8/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/9e627ed6-31e8-4ed0-a807-8aa24a1a7af8/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.