superset-sh/superset
superset-sh/supersetClick the green button below to open GitHub’s new-issue form, pre-filled with the report title, summary table, top findings, and an embedded score-card image. No authentication needed — you review on GitHub before submitting. Repobility is credited as the scanner.
This image will render at the top of the issue body. Hosted on Repobility, refreshes automatically after re-scans.
Empty Catch Block: Empty catch blocks hide errors.
Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.
## Code-quality scan: `superset-sh/superset` **Score: 61/100 (C)** · 45 findings · scanned 2026-05-14 22:55 UTC · 367,435 LOC | Severity | Count | |---|---| | CRITICAL | 2 | | HIGH | 2 | | MEDIUM | 34 | | LOW | 3 | 📊 [Full filterable report](https://repobility.com/scan/2e0fa7f3-3230-4398-84eb-683fa0568119/) ·  ### Top findings 1. **CRITICAL** `JRN001` — Token handoff appears to use a callback URL or fragment `packages/workspace-client/src/lib/eventBus.ts:71` 2. **CRITICAL** `JRN001` — Token handoff appears to use a callback URL or fragment `apps/web/src/app/auth/desktop/success/page.tsx:82` 3. **HIGH** `JRN004` — Consent is collected in UI without visible backend audit persistence `apps/desktop/src/lib/trpc/routers/workspaces/utils/git.ts:1169` 4. **HIGH** `AUC003` — Object-level route lacks visible authorization: A route with an object id-like parameter d `apps/api/src/app/api/automations/dispatch/[id]/route.ts:23` · CWE-639 · API1:2023 Broken Object Level Authorization 5. **MEDIUM** `ERR002` — Empty Catch Block: Empty catch blocks hide errors. `apps/desktop/src/renderer/routes/error.tsx:33` --- **Security note**: this issue is public. If any flagged finding is a real, exploitable vulnerability, please redirect to your `SECURITY.md` policy or open a [private security advisory](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability) instead. We're happy to close this and re-submit privately. --- _Filed automatically. Close this issue if not useful — we won't refile. Full report: https://repobility.com/scan/2e0fa7f3-3230-4398-84eb-683fa0568119/_
The button opens GitHubâs new-issue page in a new tab. You will see the title + body pre-filled â review, edit if you want, then click GitHubâs "Submit new issue" button. Repobility never posts anything on your behalf.
For real security findings on big repos: use the project's SECURITY.md or
private advisory flow instead of a public issue.