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.
Sign up free Scan another repo
50 of your 186 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 6.17s · analysis 78.44s · 16.3 MB · GitHub API rate-limit (preflight)

open-telemetry/opentelemetry-js

https://github.com/open-telemetry/opentelemetry-js · scanned 2026-06-05 21:05 UTC (4 days, 12 hours ago) · 10 languages

585 raw signals (165 security + 420 graph) 30th percentile · Typescript · large (100-500K LoC) System graph score 59 (higher by 10)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Combined
56.1
/100
Security checks
53
80 findings
System graph
59
100.0% cov · 201 findings
Critical
2
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 60.0 0.15 9.00
security_score 28.9 0.25 7.22
testing_score 95.0 0.20 19.00
documentation_score 92.0 0.15 13.80
practices_score 91.0 0.15 13.65
code_quality 69.9 0.10 6.99
Overall 1.00 69.7
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 2 High 79 Medium 37 Low 117 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 80 System graph 201 Crowd 0 Layer: Security 4 Software 105 Cicd 6 Quality 55 Frontend 48 Hardware 1 Api 62

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.

Legacy markers 2 findings
What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.
Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.
How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.
Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.
2 matching findings on this repo
  • low Old/deprecated-named symbol `PerformanceLegacy` in packages/opentelemetry-sdk-t…
  • low Old/deprecated-named symbol `PerformanceLegacy` in packages/opentelemetry-sdk-t…
View all legacy markers findings →
Commented-out code 15 findings
What it is: Lines of source that were intentionally disabled but never deleted.
Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.
How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.
Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.
12 matching findings on this repo
  • info Commented-code block (7 lines) in experimental/packages/opentelemetry-instrumen…
  • info Commented-code block (5 lines) in experimental/packages/opentelemetry-instrumen…
  • info Commented-code block (5 lines) in experimental/packages/configuration/test/File…
  • info Commented-code block (5 lines) in experimental/packages/configuration/scripts/g…
  • info Commented-code block (5 lines) in experimental/packages/configuration/src/utils…
  • info Commented-code block (7 lines) in experimental/packages/sdk-logs/test/common/ex…
  • info Commented-code block (7 lines) in experimental/packages/opentelemetry-instrumen…
  • info Commented-code block (6 lines) in experimental/packages/opentelemetry-instrumen…
  • info Commented-code block (6 lines) in experimental/packages/otlp-exporter-base/src/…
  • info Commented-code block (5 lines) in experimental/packages/otlp-transformer/test/m…
  • info Commented-code block (6 lines) in experimental/packages/otlp-transformer/test/l…
  • info Commented-code block (6 lines) in experimental/packages/otlp-transformer/test/t…
View all commented-out code findings →
Config drift 10 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.
10 matching findings on this repo
  • low File has no detected symbols: prettier.config.js
  • low File has no detected symbols: bundler-tests/browser/nextjs-15-edge/next.config.…
  • low File has no detected symbols: bundler-tests/browser/nextjs-16-edge/next.config.…
  • low Stray `console.log` in TS/JS — scripts/update-ts-configs.js:284
  • low Stray `console.log` in TS/JS — experimental/packages/configuration/scripts/gene…
  • low Very large file: experimental/packages/configuration/test/EnvironmentConfigFact…
  • low Very large file: experimental/packages/configuration/src/generated/types.ts (18…
  • info Commented-code block (5 lines) in experimental/packages/configuration/test/File…
  • info Commented-code block (5 lines) in experimental/packages/configuration/scripts/g…
  • info Commented-code block (5 lines) in experimental/packages/configuration/src/utils…
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/890f7b57-f0a7-4c37-b302-d02b01bb4096/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/890f7b57-f0a7-4c37-b302-d02b01bb4096/

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.