prometheus/prometheus

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.

Scan timing: clone 3.19s · analysis 9.58s · 27.5 MB · GitHub API rate-limit (preflight)

https://github.com/prometheus/prometheus · scanned 2026-05-23 23:58 UTC (1 week, 5 days ago) · 10 languages

416 findings (100 legacy + 316 scanner) 11/13 scanners ran 94th percentile · Go · large (100-500K LoC) Scanner says 77 (higher by 14)

File as issue Image v2 schema

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 week, 5 days ago · v2 · 258 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON

100.0% cov · 158 gaps

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`	90.0	0.20	18.00
`documentation_score`	90.0	0.15	13.50
`practices_score`	100.0	0.15	15.00
`code_quality`	70.0	0.10	7.00
Overall		1.00	91.2

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 51 Medium 20 Low 126 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 100 9-layer 158 Crowd 0 Layer: Quality 140 Security 15 Cicd 3 Software 70 Frontend 26 Network 1 Hardware 2 Api 1

Exclude dismissed / FP Exclude test files

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

Possible secret in config/testdata/uyuni_token_file.bad.yml

GapSeverity.CRITICAL Layer.SECURITY score 1.000

Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in config/testdata/uyuni_token_file.bad.yml:6; move to env var / secrets manager.

config/testdata/uyuni_token_file.bad.yml:6

Possible secret in config/testdata/conf.good.yml

GapSeverity.CRITICAL Layer.SECURITY score 1.000

Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in config/testdata/conf.good.yml:131; move to env var / secrets manager.

config/testdata/conf.good.yml:131

Possible secret in config/testdata/conf.good.yml

GapSeverity.CRITICAL Layer.SECURITY score 1.000

Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in config/testdata/conf.good.yml:224; move to env var / secrets manager.

config/testdata/conf.good.yml:224

.env file present in repo: web/ui/react-app/.env

GapSeverity.HIGH Layer.SECURITY score 0.750

Why: high severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from the file; move to env var / secrets manager.

Insecure pattern 'eval_used' in promql/functions.go:2375

GapSeverity.HIGH Layer.SECURITY score 0.413

Why: high severity · OWASP-class risk

promql/functions.go:2375

Insecure pattern 'eval_used' in promql/engine.go:1200

GapSeverity.HIGH Layer.SECURITY score 0.413

Why: high severity · OWASP-class risk

promql/engine.go:1200

Insecure pattern 'eval_used' in promql/value.go:584

GapSeverity.HIGH Layer.SECURITY score 0.413

Why: high severity · OWASP-class risk

promql/value.go:584

Insecure pattern 'eval_used' in promql/info.go:40

GapSeverity.HIGH Layer.SECURITY score 0.413

Why: high severity · OWASP-class risk

promql/info.go:40

`dangerouslySetInnerHTML` used in a React component — web/ui/mantine-ui/src/pages/query/MetricsExplorer/MetricsExplorer.tsx:126

GapSeverity.MEDIUM Layer.FRONTEND score 0.360

Why: medium severity

#10

`dangerouslySetInnerHTML` used in a React component — web/ui/react-app/src/pages/flags/Flags.tsx:108

GapSeverity.MEDIUM Layer.FRONTEND score 0.360

Why: medium severity

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

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/f49f0d4c-44f5-476f-ae97-1d983f63dbf9/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/f49f0d4c-44f5-476f-ae97-1d983f63dbf9/

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.