carbon-design-system/carbon-components-svelte
carbon-design-system/carbon-components-svelteClick 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.
Server-Side Request Forgery (SSRF) — outbound HTTP from user input
Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.
## Code-quality scan: `carbon-design-system/carbon-components-svelte` **Score: 92/100 (A-)** · 43 findings · scanned 2026-05-31 01:26 UTC · 104,571 LOC | Severity | Count | |---|---| | CRITICAL | 0 | | HIGH | 6 | | MEDIUM | 2 | | LOW | 31 | 📊 [Full filterable report](https://repobility.com/scan/64634730-a028-4945-825a-0ae00da4f842/) ·  ### Top findings 1. **HIGH** `SEC128` — Async function without await — fire-and-forget Promise (AI mistake) `src/RadioButton/RadioButtonRegistry.js:64` 2. **HIGH** `SEC128` — Async function without await — fire-and-forget Promise (AI mistake) `src/Modal/modalStore.js:27` 3. **HIGH** `SEC128` — Async function without await — fire-and-forget Promise (AI mistake) `src/DataTable/data-table-utils.js:176` 4. **HIGH** `SEC040` — innerHTML XSS — template literal with server-supplied data `scripts/release-changelog.ts:95` · CWE-79 · A03:2021 Injection (XSS) 5. **HIGH** `SEC029` — Server-Side Request Forgery (SSRF) — outbound HTTP from user input `scripts/release-changelog.ts:26` · A10:2021 SSRF --- **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/64634730-a028-4945-825a-0ae00da4f842/_
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.