GitHub Security Advisory GHSA-vvp7-h4fj-m28w discloses a high-severity path traversal vulnerability in FileBrowser Quantum that permits any authenticated user to read arbitrary files on the host system. This advisory does not affect Svelte or its dependencies.
Discover the best projects built with Svelte
What is Svelte?
Svelte compiles components to tiny vanilla JS — a reactive UI framework with minimal runtime. This gallery lists 1,538 open-source projects built with Svelte, most of them in DevTools, UI Kits and AI & ML, ranked by GitHub stars so the most-adopted repositories come first.
How projects are selected
Projects are public GitHub repositories found with the GitHub search query “topic:svelte” and at least 30 stars. Each repository is checked against Svelte’s languages and ecosystem before it is categorized, and stars, forks and last-commit dates come straight from the GitHub API, refreshed daily (current snapshot: October 6, 2026). Nothing here is paid placement.
Svelte projects: FAQ
- How many open-source Svelte projects are listed?
- 1,538 open-source projects built with Svelte are listed, sourced from public GitHub repositories as of October 6, 2026.
- What is the most-starred Svelte project on GitHub?
- open-webui leads with 151,673 GitHub stars (151.7k), followed by immich with 109,735.
- What kinds of projects are built with Svelte?
- The largest category is DevTools, with 747 projects (49% of the gallery), followed by UI Kits with 346. Projects span 14 categories in total.
- Which license do most Svelte projects use?
- MIT is the most common license, used by 946 of 1,538 projects (62%); GPL-3.0 is next with 68. 341 projects declare no recognized license.
Latest Svelte guides & deep-dives
A DNS-rebinding vulnerability in the Natural Language Toolkit (NLTK) allows SSRF attacks against internal services. SvelteKit itself is not affected, but review your Python-based data processing dependencies.
A high-severity (CVSS 7.5) advisory shows @typespec/spector exposes an unauthenticated POST /.admin/stop endpoint that exits the process. This briefing explains facts, impact, dependency-chain relevance, verification guidance, and remediation steps for maintainers and operators.


