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
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
Combined
62.7
/100
Security checks
71
68 findings
System graph
54
100.0% cov · 2761 findings
Critical
10
click to filter
Agents
10
0 votes
Crowd
0
reported
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

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

#1
Runtime dotenv file present in repo: docker/.env
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 docker/.env; move to env var / secrets manager.
docker/.env
#2
Possible secret in docs/docusaurus.config.ts
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 docs/docusaurus.config.ts:818; move to env var / secrets manager.
docs/docusaurus.config.ts:818
#3
Possible secret in superset-frontend/cypress-base/cypress/support/e2e.ts
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 superset-frontend/cypress-base/cypress/support/e2e.ts:184; move to env var / secrets manager.
superset-frontend/cypress-base/cypress/support/e2e.ts:184
#4
Possible secret in superset-frontend/src/pages/UserInfo/index.tsx
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 superset-frontend/src/pages/UserInfo/index.tsx:85; move to env var / secrets manager.
superset-frontend/src/pages/UserInfo/index.tsx:85
#5
Possible secret in superset/config.py
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 superset/config.py:1732; move to env var / secrets manager.
superset/config.py:1732
#6
Possible secret in superset/cli/test.py
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 superset/cli/test.py:80; move to env var / secrets manager.
superset/cli/test.py:80
#7
Possible secret in docker/docker-init.sh
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 docker/docker-init.sh:41; move to env var / secrets manager.
docker/docker-init.sh:41
#8
Possible secret in docker/docker-pytest-entrypoint.sh
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 docker/docker-pytest-entrypoint.sh:27; move to env var / secrets manager.
docker/docker-pytest-entrypoint.sh:27
#9
Possible secret in docker/docker-pytest-entrypoint.sh
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 docker/docker-pytest-entrypoint.sh:53; move to env var / secrets manager.
docker/docker-pytest-entrypoint.sh:53
#10
Possible secret in docker/docker-pytest-entrypoint.sh
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 docker/docker-pytest-entrypoint.sh:67; move to env var / secrets manager.
docker/docker-pytest-entrypoint.sh:67

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