esbuild-plugins-node-modules-polyfill
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): Publisher changed from maintainer to GitHub Actions CI/CD; provenance improved with SLSA attestation. | ai | |
| phantom-deps | phantom-dep:@jspm/core | AI (phantom-deps): @jspm/core is declared as a dependency and referenced in config; stable false positive. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): Husky git-hook setup accidentally published; benign dev tooling, no risk. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.8.2 | 3 / 11 | |
| 1.8.1 | 3 / 12 | |
| 1.8.0 | 3 / 16 | |
| 1.7.1 | 3 / 16 | |
| 1.7.0 | 3 / 16 | |
| 1.6.8 | 3 / 16 | |
| 1.6.7 | 3 / 16 | |
| 1.6.6 | 3 / 16 | |
| 1.6.5 | 3 / 16 | |
| 1.6.4 | 3 / 16 |
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.