esbuild-node-externals
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 | missing-githead | AI (provenance): CI publish via GitHub Actions with SLSA attestation; gitHead absence is a tooling artifact, not tampering. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Well-established package; missing description is cosmetic. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.23.1 | 1 / 8 | |
| 1.22.0 | 1 / 5 | |
| 1.21.0 | 1 / 5 | |
| 1.20.1 | 1 / 5 | |
| 1.19.1 | 1 / 5 | |
| 1.18.0 | 1 / 5 | |
| 1.17.0 | 2 / 4 | |
| 1.16.0 | 2 / 4 | |
| 1.15.0 | 2 / 4 | |
| 1.14.0 | 2 / 4 |
v1.23.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.