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 (2 weeks, 6 days ago) · 10 languages

416 raw signals (100 security + 316 graph) 11/13 scanners ran 100th percentile · Go · large (100-500K LoC) System graph score 77 (higher by 14)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 weeks, 6 days ago · v2 · 192 actionable findings from 2 signal sources. 66 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 · 157 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`	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 2 High 10 Medium 17 Low 112 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 35 System graph 157 Crowd 0 Layer: Quality 89 Security 14 Cicd 4 Software 55 Frontend 26 Network 1 Hardware 2 Api 1

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 8 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/`.

8 matching findings on this repo

info Commented-code block (5 lines) in web/ui/module/codemirror-promql/src/complete/…
info Commented-code block (8 lines) in web/ui/mantine-ui/vite.config.ts:16
info Commented-code block (6 lines) in web/ui/mantine-ui/src/pages/AlertsPage.tsx:221
info Commented-code block (6 lines) in web/ui/mantine-ui/src/pages/RulesPage.tsx:155
info Commented-code block (8 lines) in web/ui/mantine-ui/src/pages/targets/TargetsPa…
info Commented-code block (8 lines) in web/ui/mantine-ui/src/pages/service-discovery…
info Commented-code block (8 lines) in web/ui/mantine-ui/src/pages/query/QueryPanel.…
info Commented-code block (5 lines) in web/ui/mantine-ui/src/pages/query/TreeNode.ts…

View all commented-out code findings →

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

9 matching findings on this repo

low File has no detected symbols: web/ui/module/lezer-promql/rollup.config.js
low File has no detected symbols: web/ui/mantine-ui/vite.config.ts
low File has no detected symbols: web/ui/mantine-ui/vitest.config.ts
low File has no detected symbols: web/ui/mantine-ui/src/api/responseTypes/config.ts
critical Possible secret in config/testdata/uyuni_token_file.bad.yml config/testdata/uyuni_token_file.bad.yml:6
critical Possible secret in config/testdata/conf.good.yml config/testdata/conf.good.yml:131
low Very large file: config/config_test.go (3487 lines)
low Very large file: config/config.go (1790 lines)
info Commented-code block (8 lines) in web/ui/mantine-ui/vite.config.ts:16

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/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.