Installations
npm install viteReleases
create-vite@6.0.1
Published on 27 Nov 2024
v6.0.1
Published on 27 Nov 2024
create-vite@6.0.0
Published on 26 Nov 2024
plugin-legacy@6.0.0
Published on 26 Nov 2024
v6.0.0
Published on 26 Nov 2024
v6.0.0-beta.10
Published on 14 Nov 2024
Developer
Developer Guide
Module System
ESM
Min. Node Version
^18.0.0 || ^20.0.0 || >=22.0.0
Typescript Support
Yes
Node Version
20.18.1
NPM Version
10.8.2
Statistics
68,875 Stars
7,323 Commits
6,228 Forks
426 Watching
45 Branches
1,043 Contributors
Updated on 28 Nov 2024
Languages
TypeScript (82.86%)
JavaScript (10.06%)
HTML (5.18%)
CSS (1.33%)
Vue (0.16%)
AppleScript (0.12%)
Svelte (0.11%)
SCSS (0.08%)
Less (0.04%)
Stylus (0.02%)
Shell (0.01%)
Pug (0.01%)
Sass (0.01%)
Astro (0.01%)
SugarSS (0.01%)
Total Downloads
Cumulative downloads
Total Downloads
973,473,175
Last day
2.6%
3,332,350
Compared to previous day
Last week
2.4%
17,038,136
Compared to previous week
Last month
11.8%
70,790,353
Compared to previous month
Last year
149%
647,379,365
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
Peer Dependencies
11
Dev Dependencies
58
Optional Dependencies
1
Vite ⚡
Next Generation Frontend Tooling
- 💡 Instant Server Start
- ⚡️ Lightning Fast HMR
- 🛠️ Rich Features
- 📦 Optimized Build
- 🔩 Universal Plugin Interface
- 🔑 Fully Typed APIs
Vite (French word for "quick", pronounced /vit/, like "veet") is a new breed of frontend build tooling that significantly improves the frontend development experience. It consists of two major parts:
-
A dev server that serves your source files over native ES modules, with rich built-in features and astonishingly fast Hot Module Replacement (HMR).
-
A build command that bundles your code with Rollup, pre-configured to output highly optimized static assets for production.
In addition, Vite is highly extensible via its Plugin API and JavaScript API with full typing support.
Packages
| Package | Version (click for changelogs) |
|---|---|
| vite |  |
| @vitejs/plugin-legacy |  |
| create-vite |  |
Contribution
See Contributing Guide.
License
MIT.
Sponsors
Stable Version
The latest stable version of the package.
Stable Version
6.0.1
HIGH
12
8.6/10
Summary
Vite before v2.9.13 vulnerable to directory traversal via crafted URL to victim's service
Affected Versions
>= 3.0.0-alpha.0, < 3.0.0-beta.4
Patched Versions
3.0.0-beta.4
8.6/10
Summary
Vite before v2.9.13 vulnerable to directory traversal via crafted URL to victim's service
Affected Versions
< 2.9.13
Patched Versions
2.9.13
7.5/10
Summary
Vite dev server option `server.fs.deny` can be bypassed when hosted on case-insensitive filesystem
Affected Versions
>= 5.0.0, <= 5.0.11
Patched Versions
5.0.12
7.5/10
Summary
Vite dev server option `server.fs.deny` can be bypassed when hosted on case-insensitive filesystem
Affected Versions
>= 4.0.0, <= 4.5.1
Patched Versions
4.5.2
7.5/10
Summary
Vite dev server option `server.fs.deny` can be bypassed when hosted on case-insensitive filesystem
Affected Versions
>= 3.0.0, <= 3.2.7
Patched Versions
3.2.8
7.5/10
Summary
Vite dev server option `server.fs.deny` can be bypassed when hosted on case-insensitive filesystem
Affected Versions
>= 2.7.0, <= 2.9.16
Patched Versions
2.9.17
7.5/10
Summary
Vite Server Options (server.fs.deny) can be bypassed using double forward-slash (//)
Affected Versions
>= 4.3.0, < 4.3.9
Patched Versions
4.3.9
7.5/10
Summary
Vite Server Options (server.fs.deny) can be bypassed using double forward-slash (//)
Affected Versions
>= 4.2.0, < 4.2.3
Patched Versions
4.2.3
7.5/10
Summary
Vite Server Options (server.fs.deny) can be bypassed using double forward-slash (//)
Affected Versions
>= 4.1.0, < 4.1.5
Patched Versions
4.1.5
7.5/10
Summary
Vite Server Options (server.fs.deny) can be bypassed using double forward-slash (//)
Affected Versions
>= 4.0.0, < 4.0.5
Patched Versions
4.0.5
7.5/10
Summary
Vite Server Options (server.fs.deny) can be bypassed using double forward-slash (//)
Affected Versions
>= 3.0.2, < 3.2.7
Patched Versions
3.2.7
7.5/10
Summary
Vite Server Options (server.fs.deny) can be bypassed using double forward-slash (//)
Affected Versions
< 2.9.16
Patched Versions
2.9.16
MODERATE
21
5.3/10
Summary
Vite's `server.fs.deny` is bypassed when using `?import&raw`
Affected Versions
>= 5.0.0, <= 5.1.7
Patched Versions
5.1.8
5.3/10
Summary
Vite's `server.fs.deny` is bypassed when using `?import&raw`
Affected Versions
>= 5.2.0, < 5.2.14
Patched Versions
5.2.14
6.4/10
Summary
Vite DOM Clobbering gadget found in vite bundled scripts that leads to XSS
Affected Versions
>= 5.0.0, < 5.1.8
Patched Versions
5.1.8
6.4/10
Summary
Vite DOM Clobbering gadget found in vite bundled scripts that leads to XSS
Affected Versions
< 3.2.11
Patched Versions
3.2.11
6.4/10
Summary
Vite DOM Clobbering gadget found in vite bundled scripts that leads to XSS
Affected Versions
>= 5.2.0, < 5.2.14
Patched Versions
5.2.14
6.4/10
Summary
Vite DOM Clobbering gadget found in vite bundled scripts that leads to XSS
Affected Versions
>= 5.3.0, < 5.3.6
Patched Versions
5.3.6
6.4/10
Summary
Vite DOM Clobbering gadget found in vite bundled scripts that leads to XSS
Affected Versions
>= 5.4.0, < 5.4.6
Patched Versions
5.4.6
6.4/10
Summary
Vite DOM Clobbering gadget found in vite bundled scripts that leads to XSS
Affected Versions
>= 4.0.0, < 4.5.4
Patched Versions
4.5.4
5.3/10
Summary
Vite's `server.fs.deny` is bypassed when using `?import&raw`
Affected Versions
<= 3.2.10
Patched Versions
3.2.11
5.3/10
Summary
Vite's `server.fs.deny` is bypassed when using `?import&raw`
Affected Versions
>= 4.0.0, <= 4.5.3
Patched Versions
4.5.4
5.3/10
Summary
Vite's `server.fs.deny` is bypassed when using `?import&raw`
Affected Versions
>= 5.3.0, <= 5.3.5
Patched Versions
5.3.6
5.3/10
Summary
Vite's `server.fs.deny` is bypassed when using `?import&raw`
Affected Versions
>= 5.4.0, <= 5.4.5
Patched Versions
5.4.6
5.9/10
Summary
Vite's `server.fs.deny` did not deny requests for patterns with directories.
Affected Versions
>= 5.2.0, <= 5.2.5
Patched Versions
5.2.6
5.9/10
Summary
Vite's `server.fs.deny` did not deny requests for patterns with directories.
Affected Versions
>= 5.1.0, <= 5.1.6
Patched Versions
5.1.7
5.9/10
Summary
Vite's `server.fs.deny` did not deny requests for patterns with directories.
Affected Versions
>= 5.0.0, <= 5.0.12
Patched Versions
5.0.13
5.9/10
Summary
Vite's `server.fs.deny` did not deny requests for patterns with directories.
Affected Versions
>= 4.0.0, <= 4.5.2
Patched Versions
4.5.3
5.9/10
Summary
Vite's `server.fs.deny` did not deny requests for patterns with directories.
Affected Versions
>= 3.0.0, <= 3.2.8
Patched Versions
3.2.10
5.9/10
Summary
Vite's `server.fs.deny` did not deny requests for patterns with directories.
Affected Versions
>= 2.7.0, <= 2.9.17
Patched Versions
2.9.18
6.1/10
Summary
Vite XSS vulnerability in `server.transformIndexHtml` via URL payload
Affected Versions
>= 5.0.0, < 5.0.5
Patched Versions
5.0.5
6.1/10
Summary
Vite XSS vulnerability in `server.transformIndexHtml` via URL payload
Affected Versions
= 4.5.0
Patched Versions
4.5.1
6.1/10
Summary
Vite XSS vulnerability in `server.transformIndexHtml` via URL payload
Affected Versions
>= 4.4.0, < 4.4.12
Patched Versions
4.4.12
Reason
30 commit(s) and 18 issue activity found in the last 90 days -- score normalized to 10
Reason
no dangerous workflow patterns detected
Reason
license file detected
Details
- Info: project has a license file: LICENSE:0
- Info: FSF or OSI recognized license: MIT License: LICENSE:0
Reason
security policy file detected
Details
- Info: security policy file detected: github.com/vitejs/.github/SECURITY.md:1
- Info: Found linked content: github.com/vitejs/.github/SECURITY.md:1
- Info: Found disclosure, vulnerability, and/or timelines in security policy: github.com/vitejs/.github/SECURITY.md:1
- Info: Found text in security policy: github.com/vitejs/.github/SECURITY.md:1
Reason
0 existing vulnerabilities detected
Reason
Found 27/28 approved changesets -- score normalized to 9
Reason
binaries present in source code
Details
- Warn: binary detected: playground/wasm/add.wasm:1
- Warn: binary detected: playground/wasm/heavy.wasm:1
- Warn: binary detected: playground/wasm/light.wasm:1
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Info: jobLevel 'contents' permission set to 'read': .github/workflows/publish.yml:16
- Info: found token with 'none' permissions: .github/workflows/ci.yml:1
- Warn: no topLevel permission defined: .github/workflows/ecosystem-ci-trigger.yml:1
- Warn: no topLevel permission defined: .github/workflows/issue-close-require.yml:1
- Warn: no topLevel permission defined: .github/workflows/issue-labeled.yml:1
- Warn: no topLevel permission defined: .github/workflows/publish.yml:1
- Warn: no topLevel permission defined: .github/workflows/release-tag.yml:1
- Warn: no topLevel permission defined: .github/workflows/semantic-pull-request.yml:1
- Info: no jobLevel write permissions found
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:44: update your workflow using https://app.stepsecurity.io/secureworkflow/vitejs/vite/ci.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:80: update your workflow using https://app.stepsecurity.io/secureworkflow/vitejs/vite/ci.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/ci.yml:83: update your workflow using https://app.stepsecurity.io/secureworkflow/vitejs/vite/ci.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:86: update your workflow using https://app.stepsecurity.io/secureworkflow/vitejs/vite/ci.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:109: update your workflow using https://app.stepsecurity.io/secureworkflow/vitejs/vite/ci.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:153: update your workflow using https://app.stepsecurity.io/secureworkflow/vitejs/vite/ci.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/ci.yml:156: update your workflow using https://app.stepsecurity.io/secureworkflow/vitejs/vite/ci.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:159: update your workflow using https://app.stepsecurity.io/secureworkflow/vitejs/vite/ci.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ecosystem-ci-trigger.yml:12: update your workflow using https://app.stepsecurity.io/secureworkflow/vitejs/vite/ecosystem-ci-trigger.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ecosystem-ci-trigger.yml:48: update your workflow using https://app.stepsecurity.io/secureworkflow/vitejs/vite/ecosystem-ci-trigger.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/ecosystem-ci-trigger.yml:64: update your workflow using https://app.stepsecurity.io/secureworkflow/vitejs/vite/ecosystem-ci-trigger.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ecosystem-ci-trigger.yml:69: update your workflow using https://app.stepsecurity.io/secureworkflow/vitejs/vite/ecosystem-ci-trigger.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/issue-close-require.yml:13: update your workflow using https://app.stepsecurity.io/secureworkflow/vitejs/vite/issue-close-require.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/issue-labeled.yml:14: update your workflow using https://app.stepsecurity.io/secureworkflow/vitejs/vite/issue-labeled.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/issue-labeled.yml:23: update your workflow using https://app.stepsecurity.io/secureworkflow/vitejs/vite/issue-labeled.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/issue-labeled.yml:32: update your workflow using https://app.stepsecurity.io/secureworkflow/vitejs/vite/issue-labeled.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/issue-labeled.yml:41: update your workflow using https://app.stepsecurity.io/secureworkflow/vitejs/vite/issue-labeled.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/lock-closed-issues.yml:15: update your workflow using https://app.stepsecurity.io/secureworkflow/vitejs/vite/lock-closed-issues.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/preview-release.yml:26: update your workflow using https://app.stepsecurity.io/secureworkflow/vitejs/vite/preview-release.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/preview-release.yml:29: update your workflow using https://app.stepsecurity.io/secureworkflow/vitejs/vite/preview-release.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/publish.yml:21: update your workflow using https://app.stepsecurity.io/secureworkflow/vitejs/vite/publish.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/publish.yml:24: update your workflow using https://app.stepsecurity.io/secureworkflow/vitejs/vite/publish.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/publish.yml:27: update your workflow using https://app.stepsecurity.io/secureworkflow/vitejs/vite/publish.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release-tag.yml:17: update your workflow using https://app.stepsecurity.io/secureworkflow/vitejs/vite/release-tag.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/release-tag.yml:42: update your workflow using https://app.stepsecurity.io/secureworkflow/vitejs/vite/release-tag.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/semantic-pull-request.yml:17: update your workflow using https://app.stepsecurity.io/secureworkflow/vitejs/vite/semantic-pull-request.yml/main?enable=pin
- Warn: downloadThenRun not pinned by hash: .github/workflows/ci.yml:185
- Info: 0 out of 13 GitHub-owned GitHubAction dependencies pinned
- Info: 1 out of 14 third-party GitHubAction dependencies pinned
- Info: 0 out of 1 downloadThenRun dependencies pinned
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 29 are checked with a SAST tool
Score
6.1
/10
Last Scanned on 2024-11-18
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More