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.

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

apache/superset

https://github.com/apache/superset · scanned 2026-06-17 01:39 UTC (1 month, 1 week ago) · 10 languages

2936 raw signals (142 security + 2794 graph) 11/13 scanners ran 17th percentile · Typescript · medium (20-100K LoC)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 1 week ago · v3 · 2829 actionable findings from 2 signal sources. 107 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 · 2761 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	100.0	0.25	25.00
`testing_score`	76.0	0.20	15.20
`documentation_score`	83.0	0.15	12.45
`practices_score`	79.0	0.15	11.85
`code_quality`	71.0	0.10	7.10
Overall		1.00	80.6

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 10 High 17 Medium 77 Low 368 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 68 System graph 2761 Crowd 0 Layer: Quality 2583 Security 58 Cicd 9 Software 22 Frontend 147 Hardware 7 Api 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.

Duplicates & near-duplicates 6 findings

What it is: Same function copy-pasted into multiple modules with minor variations.

Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.

How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.

Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.

6 matching findings on this repo

low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 3 places repo-level
low Near-duplicate function bodies in 28 places
low Near-duplicate function bodies in 27 places
low Near-duplicate function bodies in 4 places
low Near-duplicate function bodies in 11 places

View all duplicates & near-duplicates findings →

Legacy markers 34 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 — superset-frontend/plugins/legacy-plugin-ch…
info TODO/FIXME marker in shipping code — superset-frontend/plugins/legacy-preset-ch…
info TODO/FIXME marker in shipping code — superset-frontend/plugins/legacy-plugin-ch…
medium Insecure pattern 'direct_innerhtml_assignment' in superset-frontend/plugins/leg… superset-frontend/plugins/legacy-preset-chart-nvd…:291
medium Insecure pattern 'direct_innerhtml_assignment' in superset-frontend/plugins/leg… superset-frontend/plugins/legacy-plugin-chart-cho…:44
low Node manifest has dependencies but no lockfile: superset-frontend/plugins/legac… superset-frontend/plugins/legacy-plugin-chart-par…
low Node manifest has dependencies but no lockfile: superset-frontend/plugins/legac… superset-frontend/plugins/legacy-plugin-chart-cal…
low Node manifest has dependencies but no lockfile: superset-frontend/plugins/legac… superset-frontend/plugins/legacy-plugin-chart-hor…
low Node manifest has dependencies but no lockfile: superset-frontend/plugins/legac… superset-frontend/plugins/legacy-plugin-chart-pai…
low Node manifest has dependencies but no lockfile: superset-frontend/plugins/legac… superset-frontend/plugins/legacy-plugin-chart-ros…
low Node manifest has dependencies but no lockfile: superset-frontend/plugins/legac… superset-frontend/plugins/legacy-plugin-chart-par…
low Node manifest has dependencies but no lockfile: superset-frontend/plugins/legac… superset-frontend/plugins/legacy-preset-chart-nvd…

View all legacy markers findings →

Commented-out code 2199 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 setup.py:1
info Commented-code block (7 lines) in superset-core/src/superset_core/__init__.py:1
info Commented-code block (7 lines) in superset-core/src/superset_core/extensions/ty…
info Commented-code block (7 lines) in superset-core/src/superset_core/extensions/__…
info Commented-code block (7 lines) in superset-core/src/superset_core/extensions/co…
info Commented-code block (7 lines) in superset-core/src/superset_core/semantic_laye…
info Commented-code block (7 lines) in superset-core/src/superset_core/semantic_laye…
info Commented-code block (7 lines) in superset-core/src/superset_core/semantic_laye…
info Commented-code block (7 lines) in superset-core/src/superset_core/semantic_laye…
info Commented-code block (7 lines) in superset-core/src/superset_core/semantic_laye…
info Commented-code block (7 lines) in superset-core/src/superset_core/semantic_laye…
info Commented-code block (7 lines) in superset-core/src/superset_core/semantic_laye…

View all commented-out code findings →

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

low Possibly dead Python function: build_configuration_schema superset-core/src/superset_core/semantic_layers/c…
info TODO/FIXME marker in shipping code — superset-frontend/webpack.config.js:469
low Stray `console.log` in TS/JS — superset-frontend/webpack.config.js:663
info TODO/FIXME marker in shipping code — superset-frontend/cypress-base/cypress.con…
info TODO/FIXME marker in shipping code — superset-frontend/src/dashboard/components…
info TODO/FIXME marker in shipping code — superset-frontend/src/dashboard/components…
info TODO/FIXME marker in shipping code — superset-frontend/src/dashboard/components…
info TODO/FIXME marker in shipping code — superset-frontend/src/explore/components/c…
info TODO/FIXME marker in shipping code — superset-frontend/src/explore/controlUtils…
critical Possible secret in docs/docusaurus.config.ts docs/docusaurus.config.ts:818
medium Insecure pattern 'direct_innerhtml_assignment' in superset-frontend/src/utils/h… superset-frontend/src/utils/hostNamesConfig.test.…:28
critical Possible secret in superset/config.py superset/config.py:1732

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/5d27214b-831a-4ed2-ab07-27c1fa98ec8e/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/5d27214b-831a-4ed2-ab07-27c1fa98ec8e/

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.