@netlify/plugins-list
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 6.81.8 | 0 / 17 | |
| 6.81.7 | 0 / 17 | |
| 6.81.6 | 0 / 17 | |
| 6.81.5 | 0 / 17 | |
| 6.81.3 | 0 / 17 | |
| 6.81.2 | 0 / 17 | |
| 6.81.1 | 0 / 17 | |
| 6.80.0 | 0 / 17 | |
| 6.79.0 | 0 / 17 | |
| 6.78.1 | 0 / 17 | |
| 6.78.0 | 0 / 17 |
v6.81.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.80.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.79.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.78.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.78.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.