@aws-cdk/cfnspec
The CloudFormation resource specification used by @aws-cdk packages
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:build-tools/validate-evolution.js | AI (source-diff): File is readable TypeScript/JS build tooling for spec evolution validation; long lines are likely JSON/data content, not obfuscation. False positive for this AWS CDK package. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process usage is confined to build-tools/create-missing-libraries.js, a build-time scaffolding utility in the aws-cdk monorepo. Not runtime code; stable false positive for this package. | ai | |
| semgrep | semgrep:child-process-spawn | AI (semgrep): spawn() is in a build-time exec() helper in build-tools/create-missing-libraries.js. Expected pattern for monorepo build tooling; not a runtime risk. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in build-tools scripts loads package.json files from known monorepo paths — a standard build-time pattern, not a runtime security risk. Stable for this package. | ai |
Versions (showing 89 of 389)
| Version | Deps | Published |
|---|---|---|
| 1.32.1 | 1 / 10 | |
| 1.32.0 | 1 / 10 | |
| 1.31.0 | 1 / 10 | |
| 1.30.0 | 1 / 10 | |
| 1.29.0 | 1 / 10 | |
| 1.28.0 | 1 / 10 | |
| 1.27.0 | 1 / 10 | |
| 1.26.0 | 1 / 10 | |
| 1.25.0 | 1 / 10 | |
| 1.24.0 | 1 / 10 | |
| 1.23.0 | 1 / 10 | |
| 1.22.0 | 1 / 10 | |
| 1.21.1 | 1 / 10 | |
| 1.21.0 | 1 / 10 | |
| 1.20.0 | 1 / 10 | |
| 1.19.0 | 1 / 8 | |
| 1.18.0 | 1 / 8 | |
| 1.17.1 | 1 / 8 | |
| 1.17.0 | 1 / 8 | |
| 1.16.3 | 1 / 8 | |
| 1.16.2 | 1 / 8 | |
| 1.16.1 | 1 / 8 | |
| 1.16.0 | 1 / 8 | |
| 1.15.0 | 1 / 8 | |
| 1.14.0 | 1 / 8 | |
| 1.13.1 | 1 / 8 | |
| 1.13.0 | 1 / 8 | |
| 1.12.0 | 1 / 8 | |
| 1.11.0 | 1 / 8 | |
| 1.10.1 | 1 / 8 | |
| 1.10.0 | 1 / 8 | |
| 1.9.0 | 1 / 8 | |
| 1.8.0 | 1 / 8 | |
| 1.7.0 | 1 / 8 | |
| 1.6.1 | 1 / 8 | |
| 1.6.0 | 1 / 8 | |
| 1.5.0 | 1 / 8 | |
| 1.4.0 | 1 / 8 | |
| 1.3.0 | 1 / 8 | |
| 1.2.0 | 1 / 8 | |
| 1.1.0 | 1 / 8 | |
| 1.0.0 | 1 / 8 | |
| 0.39.0 | 1 / 8 | |
| 0.38.0 | 1 / 8 | |
| 0.37.0 | 1 / 8 | |
| 0.36.2 | 1 / 8 | |
| 0.36.1 | 1 / 8 | |
| 0.36.0 | 1 / 8 | |
| 0.35.0 | 1 / 8 | |
| 0.34.0 | 1 / 8 | |
| 0.33.0 | 1 / 8 | |
| 0.32.0 | 1 / 8 | |
| 0.31.0 | 1 / 8 | |
| 0.30.0 | 1 / 8 | |
| 0.29.0 | 1 / 8 | |
| 0.28.0 | 1 / 8 | |
| 0.27.0 | 1 / 8 | |
| 0.26.0 | 1 / 8 | |
| 0.25.3 | 1 / 8 | |
| 0.25.2 | 1 / 8 | |
| 0.25.1 | 1 / 8 | |
| 0.25.0 | 1 / 8 | |
| 0.24.1 | 1 / 8 | |
| 0.24.0 | 1 / 8 | |
| 0.23.0 | 1 / 8 | |
| 0.22.0 | 1 / 8 | |
| 0.21.0 | 1 / 8 | |
| 0.20.0 | 1 / 8 | |
| 0.19.0 | 1 / 8 | |
| 0.18.1 | 1 / 8 | |
| 0.18.0 | 1 / 8 | |
| 0.17.0 | 1 / 8 | |
| 0.16.0 | 1 / 8 | |
| 0.15.2 | 1 / 8 | |
| 0.15.1 | 1 / 8 | |
| 0.15.0 | 1 / 8 | |
| 0.14.1 | 1 / 8 | |
| 0.14.0 | 1 / 8 | |
| 0.13.0 | 1 / 8 | |
| 0.12.0 | 1 / 8 | |
| 0.11.0 | 1 / 8 | |
| 0.10.0 | 1 / 8 | |
| 0.9.2 | 1 / 8 | |
| 0.9.1 | 1 / 8 | |
| 0.9.0 | 1 / 8 | |
| 0.8.2 | 1 / 8 | |
| 0.8.1 | 1 / 8 | |
| 0.8.0 | 1 / 7 | |
| 2.105.0-alpha.0 | 2 / 10 |
v1.32.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.1
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.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.1
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.
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.
v1.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
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.