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
116 of your 324 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.
Upstream (GitHub) caused delay on this scan — not Repobility.
  • GitHub API rate-limited (HTTP 403) — preflight skipped, fell back to direct git clone.
  • Clone from GitHub took 70.98s for a 183.4 MB repo slow.
  • Repobility's analysis ran in 46.72s after the clone landed.

grafana/grafana

https://github.com/grafana/grafana · scanned 2026-06-05 07:47 UTC (5 days, 22 hours ago) · 10 languages

2873 raw signals (291 security + 2582 graph) 11/13 scanners ran 93rd percentile · Typescript · huge (>500K LoC) System graph score 43 (higher by 49)

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

Complete repo analysis

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

JSON
Combined
67.9
/100
Security checks
92
76 findings
System graph
43
100.0% cov · 1092 findings
Critical
25
click to filter
Agents
6
0 votes
Crowd
0
reported
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 80.0 0.10 8.00
Overall 1.00 92.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 25 High 39 Medium 137 Low 396 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 76 System graph 1092 Crowd 0 Layer: Quality 417 Security 68 Cicd 26 Software 59 Frontend 530 Network 15 Hardware 42 Api 11

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 22 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.
12 matching findings on this repo
  • info TODO/FIXME marker in shipping code — packages/grafana-ui/src/themes/GlobalStyle…
  • info TODO/FIXME marker in shipping code — packages/grafana-ui/src/components/Forms/L…
  • info TODO/FIXME marker in shipping code — public/app/features/templating/LegacyVaria…
  • low Very large file: packages/grafana-api-clients/src/clients/rtkq/legacy/endpoints…
  • low Old/deprecated-named symbol `getStylesLegacy` in packages/grafana-flamegraph/sr…
  • low Old/deprecated-named symbol `TeamDtoLegacy` in public/app/types/teams.ts:1
  • low Old/deprecated-named symbol `useDeleteFoldersMutationLegacy` in public/app/api/…
  • low Old/deprecated-named symbol `useDeleteFolderMutationLegacy` in public/app/api/c…
  • low Old/deprecated-named symbol `createShortLinkLegacy` in public/app/core/utils/sh…
  • low Old/deprecated-named symbol `useFoldersQueryLegacy` in public/app/core/componen…
  • low Old/deprecated-named symbol `useFoldersQueryLegacy` in public/app/core/componen…
  • low Old/deprecated-named symbol `PublicDashboardBadgeLegacy` in public/app/features…
View all legacy markers findings →
Commented-out code 129 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 (5 lines) in knip.config.ts:49
  • info Commented-code block (11 lines) in eslint.config.js:687
  • info Commented-code block (8 lines) in apps/example/plugin/src/generated/example/v1a…
  • info Commented-code block (6 lines) in apps/example/plugin/src/generated/examplekind…
  • info Commented-code block (6 lines) in e2e-playwright/panels-suite/panelEdit_transfo…
  • info Commented-code block (5 lines) in packages/grafana-alerting/tests/provider.tsx:…
  • info Commented-code block (9 lines) in packages/grafana-data/src/themes/createVisual…
  • info Commented-code block (7 lines) in packages/grafana-data/src/field/fieldDisplay.…
  • info Commented-code block (5 lines) in packages/grafana-data/src/field/displayProces…
  • info Commented-code block (5 lines) in packages/grafana-data/src/field/fieldOverride…
  • info Commented-code block (5 lines) in packages/grafana-data/src/transformations/tra…
  • info Commented-code block (6 lines) in packages/grafana-e2e-selectors/src/selectors/…
View all commented-out code findings →
Config drift 32 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.
12 matching findings on this repo
  • high [SEC027] XML External Entity (XXE) — Node.js xml parsers: Node.js XML parsers c… e2e-playwright/test-plugins/frontend-sandbox-pane…:94
  • low File has no detected symbols: playwright.storybook.config.ts
  • low File has no detected symbols: jest.config.js
  • low File has no detected symbols: stylelint.config.js
  • low File has no detected symbols: i18next.config.ts
  • low File has no detected symbols: knip.config.ts
  • low File has no detected symbols: scripts/webpack/postcss.config.js
  • info TODO/FIXME marker in shipping code — jest.config.codeowner.js:112
  • low Stray `console.log` in TS/JS — jest.config.codeowner.js:68
  • info TODO/FIXME marker in shipping code — knip.config.ts:25
  • info TODO/FIXME marker in shipping code — eslint.config.js:1
  • info TODO/FIXME marker in shipping code — packages/grafana-plugin-configs/webpack.co…
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/ed158104-2de3-4a38-8f2c-932dd63d62b0/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/ed158104-2de3-4a38-8f2c-932dd63d62b0/

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.