@netlify/vite-plugin
51
Versions
—
License
No
Install Scripts
Verified
Provenance
Supply chain provenance
Status for the latest visible version.
SLSA provenance attestation
npm registry signatures
gitHead linked
Maintainers
netlify-botmikewenyouvalvserhalp-netlifymlgualtieri-gatsby
Keywords
netlifyvite-plugindev
Versions (showing 51 of 93)
| Version | Deps | Published |
|---|---|---|
| 2.12.9 | 3 / 5 | |
| 2.12.7 | 3 / 5 | |
| 2.12.6 | 3 / 5 | |
| 2.12.5 | 3 / 5 | |
| 2.12.4 | 3 / 5 | |
| 2.12.3 | 3 / 5 | |
| 2.12.2 | 3 / 5 | |
| 2.12.1 | 3 / 5 | |
| 2.12.0 | 3 / 5 | |
| 2.11.7 | 3 / 5 | |
| 2.11.6 | 3 / 5 | |
| 2.11.5 | 3 / 5 | |
| 2.11.4 | 3 / 5 | |
| 2.11.3 | 3 / 5 | |
| 2.11.2 | 3 / 5 | |
| 2.11.1 | 3 / 5 | |
| 2.11.0 | 3 / 5 | |
| 2.10.11 | 3 / 5 | |
| 2.10.10 | 3 / 5 | |
| 2.10.9 | 3 / 5 | |
| 2.10.8 | 3 / 5 | |
| 2.10.7 | 3 / 5 | |
| 2.10.6 | 3 / 5 | |
| 2.10.5 | 3 / 5 | |
| 2.10.4 | 3 / 5 | |
| 2.10.3 | 3 / 5 | |
| 2.10.2 | 3 / 5 | |
| 2.10.1 | 3 / 5 | |
| 2.10.0 | 3 / 5 | |
| 2.9.0 | 3 / 5 | |
| 2.8.0 | 3 / 5 | |
| 2.7.20 | 3 / 5 | |
| 2.7.19 | 3 / 5 | |
| 2.7.18 | 3 / 5 | |
| 2.7.17 | 3 / 5 | |
| 2.7.16 | 3 / 5 | |
| 2.7.15 | 3 / 5 | |
| 2.7.14 | 3 / 5 | |
| 2.7.13 | 3 / 5 | |
| 2.7.12 | 3 / 5 | |
| 2.7.11 | 3 / 5 | |
| 2.7.10 | 3 / 5 | |
| 2.7.9 | 3 / 5 | |
| 2.7.8 | 3 / 5 | |
| 2.7.7 | 3 / 5 | |
| 2.7.6 | 3 / 5 | |
| 2.7.5 | 3 / 5 | |
| 2.7.4 | 3 / 5 | |
| 2.7.3 | 3 / 5 | |
| 2.7.2 | 3 / 5 | |
| 2.7.1 | 3 / 5 |
v2.12.9
2 findings
INFO
Has SLSA provenance attestation
provenance
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
INFO
Publisher changed: netlify-bot → GitHub Actions (on 2026-07-17, now via trusted publisher with provenance)
provenance
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (netlify-bot) on 2026-07-17, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.