SUPPLY-CHAIN REPORT

sveltejs/svelte

web development for the rest of us

VERDICTCLEAN·85/100

View on GitHub →

STARS

86,325

FORKS

4,888

OPEN ISSUES

990

LANGUAGE

JavaScript

LICENSE

MIT

LAST PUSH

2026-04-17

SIGNALS

Historical supply-chain incidents

No known compromise, backdoor, or wallet-drainer incident in our curated DB.

INFO

Historical security advisories

9 disclosed advisories (0 critical, 1 high) — typically patched in newer releases. Pin to the latest version.

Maintenance activity

Actively maintained. Last push 0 days ago.

Ecosystem trust

86,325 stars. Widely used — supply-chain attacks on popular repos are high-impact but also more likely to be caught fast.

License

MIT

METHODOLOGY

This report is generated on demand by querying the GitHub API for repository metadata and published security advisories, then cross-referencing our curated database of known supply-chain incidents (xz-utils, event-stream, ua-parser-js, colors.js, tj-actions, Codecov, and more). Results are cached for 24 hours. We do not scan repository code or dependencies — for that, see Snyk or Socket. Verdict: CLEAN ≥80, CAUTION 50–79, COMPROMISED<50.

SCAN A DEPLOYED SITE

Repo looks clean but the live deployment might still be exposing headers, CORS, or SSL misconfigurations.

SCAN A URL →

SCANNING sveltejs/svelte...