@vitejs/plugin-react
The default Vite plugin for React projects
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Legitimate migration from vitebot to GitHub Actions CI/CD publishing with SLSA provenance attestation for the official Vite org. | ai | |
| phantom-deps | phantom-dep:react-refresh | AI (phantom-deps): Declared dependency loaded dynamically at runtime by the plugin; standard pattern for Babel/React refresh integration. | ai | |
| phantom-deps | phantom-dep:@types/babel__core | AI (phantom-deps): TypeScript type declaration package; consumed at build time, not directly imported at runtime. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-transform-react-jsx-self | AI (phantom-deps): Babel plugin loaded dynamically via Babel config; standard pattern for this package. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-transform-react-jsx-source | AI (phantom-deps): Babel plugin loaded dynamically via Babel config; standard pattern for this package. | ai |
Versions (showing 51 of 62)
| Version | Deps | Published |
|---|---|---|
| 6.0.2 | 1 / 9 | |
| 6.0.1 | 1 / 9 | |
| 6.0.0 | 1 / 9 | |
| 5.2.0 | 6 / 6 | |
| 5.1.4 | 6 / 6 | |
| 5.1.3 | 6 / 6 | |
| 5.1.2 | 6 / 6 | |
| 5.1.1 | 6 / 6 | |
| 5.1.0 | 6 / 6 | |
| 5.0.4 | 6 / 7 | |
| 5.0.3 | 6 / 7 | |
| 5.0.2 | 6 / 7 | |
| 5.0.1 | 6 / 7 | |
| 5.0.0 | 6 / 7 | |
| 4.7.0 | 6 / 7 | |
| 4.6.0 | 6 / 7 | |
| 4.5.2 | 6 / 2 | |
| 4.5.1 | 6 / 2 | |
| 4.5.0 | 6 / 2 | |
| 4.4.1 | 5 / 2 | |
| 4.4.0 | 5 / 2 | |
| 4.3.4 | 5 / 1 | |
| 4.3.3 | 5 / 1 | |
| 4.3.2 | 5 / 1 | |
| 4.3.1 | 5 / 1 | |
| 4.3.0 | 5 / 1 | |
| 4.2.1 | 5 / 0 | |
| 4.2.0 | 5 / 0 | |
| 4.1.1 | 5 / 0 | |
| 4.1.0 | 5 / 0 | |
| 4.0.4 | 4 / 0 | |
| 4.0.3 | 4 / 0 | |
| 4.0.2 | 4 / 0 | |
| 4.0.1 | 4 / 0 | |
| 4.0.0 | 4 / 0 | |
| 3.1.0 | 5 / 0 | |
| 3.0.1 | 5 / 0 | |
| 3.0.0 | 5 / 0 | |
| 2.2.0 | 7 / 1 | |
| 2.1.0 | 7 / 1 | |
| 2.0.1 | 7 / 1 | |
| 2.0.0 | 7 / 1 | |
| 1.3.2 | 8 / 0 | |
| 1.3.1 | 8 / 0 | |
| 1.3.0 | 8 / 0 | |
| 1.2.0 | 8 / 0 | |
| 1.1.4 | 8 / 0 | |
| 1.1.3 | 8 / 0 | |
| 1.1.2 | 8 / 0 | |
| 1.1.1 | 8 / 0 | |
| 1.1.0 | 8 / 0 |
v6.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.4
2 findingsThis version was published by a different npm account than previous versions on 2025-09-27. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.7.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.