jaegertracing/jaeger-ui

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.

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

Scan timing: clone 2.62s · analysis 48.7s · 5.8 MB · GitHub API rate-limit (preflight)

https://github.com/jaegertracing/jaeger-ui · scanned 2026-06-05 18:30 UTC (4 days, 19 hours ago) · 10 languages

319 raw signals (87 security + 232 graph) 61st percentile · Typescript · medium (20-100K LoC) System graph score 85 (lower by 11)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 19 hours ago · v2 · 162 actionable findings from 2 signal sources. 41 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 · 113 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	62.4	0.25	15.60
`testing_score`	93.0	0.20	18.60
`documentation_score`	85.0	0.15	12.75
`practices_score`	76.0	0.15	11.40
`code_quality`	67.0	0.10	6.70
Overall		1.00	74.0

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 12 Medium 14 Low 71 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 49 System graph 113 Crowd 0 Layer: Software 75 Cicd 9 Security 5 Quality 47 Api 1 Frontend 22 Hardware 3

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.

Commented-out code 27 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 (13 lines) in scripts/get-tracking-version.js:77
info Commented-code block (6 lines) in packages/jaeger-ui/jaeger-ui.config.console-a…
info Commented-code block (10 lines) in packages/jaeger-ui/src/types/config.ts:27
info Commented-code block (6 lines) in packages/jaeger-ui/src/stores/trace-diff-stor…
info Commented-code block (8 lines) in packages/jaeger-ui/src/utils/prefix-url.test.…
info Commented-code block (6 lines) in packages/jaeger-ui/src/utils/embedded-url.ts:…
info Commented-code block (5 lines) in packages/jaeger-ui/src/utils/tracking/error-c…
info Commented-code block (9 lines) in packages/jaeger-ui/src/utils/DraggableManager…
info Commented-code block (9 lines) in packages/jaeger-ui/src/components/common/Filt…
info Commented-code block (6 lines) in packages/jaeger-ui/src/components/PlexusDemo/…
info Commented-code block (5 lines) in packages/jaeger-ui/src/components/TracePage/T…
info Commented-code block (5 lines) in packages/jaeger-ui/src/components/TracePage/T…

View all commented-out code findings →

Config drift 7 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.

7 matching findings on this repo

low File has no detected symbols: vite.config.ts
low File has no detected symbols: knip.config.ts
low File has no detected symbols: packages/jaeger-ui/src/types/config.ts
low File has no detected symbols: packages/jaeger-ui/src/constants/default-config.ts
info TODO/FIXME marker in shipping code — packages/jaeger-ui/src/types/config.ts:154
info Commented-code block (6 lines) in packages/jaeger-ui/jaeger-ui.config.console-a…
info Commented-code block (10 lines) in packages/jaeger-ui/src/types/config.ts:27

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/2f42f232-d679-4f41-911a-02f895fe63c7/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/2f42f232-d679-4f41-911a-02f895fe63c7/

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.