@pulumi/policy
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Pattern reads caller's package.json for version detection; not arbitrary module loading. Stable for this package. | ai | |
| phantom-deps | phantom-dep:protobufjs | AI (phantom-deps): protobufjs is a declared runtime dependency; likely used transitively or via generated code rather than direct import. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.21.0 | 3 / 10 | |
| 1.20.0 | 3 / 10 | |
| 1.19.0 | 3 / 10 | |
| 1.18.1 | 3 / 10 | |
| 1.18.0 | 3 / 10 | |
| 1.17.0 | 4 / 10 | |
| 1.16.0 | 4 / 10 |
v1.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.