@gradientedge/cdk-utils-cloudflare
Cloudflare Pulumi utilities for @gradientedge/cdk-utils
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@pulumi/cloudflare | AI (dependencies): @pulumi/cloudflare is the official Pulumi Cloudflare provider; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): New package from an org that doesn't yet publish with Sigstore; no other risk signals present. | ai | |
| phantom-deps | phantom-dep:@types/lodash | AI (phantom-deps): @types/lodash is a type-only dev dependency; not directly imported at runtime is expected behavior. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 2.12.1 | 10 / 0 | |
| 2.8.1 | 10 / 0 | |
| 2.8.0 | 10 / 0 | |
| 2.7.0 | 10 / 0 | |
| 2.6.0 | 10 / 0 | |
| 2.5.0 | 10 / 0 | |
| 2.4.0 | 10 / 0 | |
| 2.2.0 | 10 / 0 | |
| 2.1.0 | 10 / 0 | |
| 2.0.0 | 10 / 0 | |
| 1.0.1 | 10 / 0 | |
| 1.0.0 | 10 / 0 |
v2.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.