@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 100 of 388)
| Version | Deps | Published |
|---|---|---|
| 2.72.1 | 2 / 9 | |
| 2.72.0 | 2 / 9 | |
| 2.71.0 | 2 / 9 | |
| 2.70.0 | 2 / 9 | |
| 2.69.0 | 2 / 9 | |
| 2.68.0 | 2 / 9 | |
| 2.67.0 | 2 / 9 | |
| 2.66.1 | 2 / 9 | |
| 2.66.0 | 2 / 9 | |
| 2.65.0 | 2 / 9 | |
| 2.64.0 | 2 / 9 | |
| 2.63.2 | 2 / 9 | |
| 2.63.1 | 2 / 9 | |
| 2.63.0 | 2 / 9 | |
| 2.62.2 | 2 / 9 | |
| 2.62.1 | 2 / 9 | |
| 2.62.0 | 2 / 9 | |
| 2.61.1 | 2 / 9 | |
| 2.61.0 | 2 / 9 | |
| 2.60.0 | 2 / 9 | |
| 2.59.0 | 2 / 9 | |
| 2.58.1 | 2 / 9 | |
| 2.58.0 | 2 / 9 | |
| 2.57.0 | 2 / 9 | |
| 2.56.1 | 2 / 9 | |
| 2.56.0 | 2 / 9 | |
| 2.55.1 | 2 / 9 | |
| 2.55.0 | 2 / 9 | |
| 2.54.0 | 2 / 9 | |
| 2.53.0 | 2 / 9 | |
| 2.52.1 | 2 / 9 | |
| 2.52.0 | 2 / 9 | |
| 2.51.1 | 2 / 9 | |
| 2.51.0 | 2 / 9 | |
| 2.50.0 | 2 / 9 | |
| 2.49.1 | 2 / 9 | |
| 2.49.0 | 2 / 9 | |
| 2.48.0 | 2 / 9 | |
| 2.47.0 | 2 / 9 | |
| 2.46.0 | 2 / 9 | |
| 2.45.0 | 2 / 9 | |
| 2.44.0 | 2 / 9 | |
| 2.43.1 | 2 / 9 | |
| 2.43.0 | 2 / 9 | |
| 2.42.1 | 2 / 9 | |
| 2.42.0 | 2 / 9 | |
| 2.41.0 | 2 / 9 | |
| 2.40.0 | 2 / 9 | |
| 2.39.1 | 2 / 9 | |
| 2.39.0 | 2 / 9 | |
| 2.38.1 | 2 / 9 | |
| 2.38.0 | 2 / 9 | |
| 2.37.1 | 2 / 9 | |
| 2.37.0 | 2 / 9 | |
| 2.36.0 | 2 / 9 | |
| 2.35.0 | 2 / 9 | |
| 2.34.2 | 2 / 9 | |
| 2.34.1 | 2 / 9 | |
| 2.34.0 | 2 / 9 | |
| 2.33.0 | 2 / 9 | |
| 2.32.1 | 2 / 9 | |
| 2.32.0 | 2 / 9 | |
| 2.31.2 | 2 / 9 | |
| 2.31.1 | 2 / 9 | |
| 2.31.0 | 2 / 9 | |
| 2.30.0 | 2 / 9 | |
| 2.29.1 | 2 / 9 | |
| 2.29.0 | 2 / 9 | |
| 2.28.1 | 2 / 9 | |
| 2.28.0 | 2 / 9 | |
| 2.27.0 | 2 / 9 | |
| 2.26.0 | 2 / 9 | |
| 2.25.0 | 2 / 9 | |
| 2.24.1 | 2 / 9 | |
| 2.24.0 | 2 / 9 | |
| 2.23.0 | 2 / 9 | |
| 2.22.0 | 2 / 9 | |
| 2.21.1 | 2 / 9 | |
| 2.21.0 | 2 / 9 | |
| 2.20.0 | 2 / 9 | |
| 2.19.0 | 2 / 9 | |
| 2.18.0 | 2 / 9 | |
| 2.17.0 | 2 / 9 | |
| 2.16.0 | 2 / 9 | |
| 2.15.0 | 2 / 9 | |
| 2.14.0 | 2 / 9 | |
| 2.13.0 | 2 / 9 | |
| 2.12.0 | 2 / 9 | |
| 2.11.0 | 2 / 9 | |
| 2.10.0 | 2 / 9 | |
| 2.9.0 | 2 / 9 | |
| 2.8.0 | 2 / 9 | |
| 2.7.0 | 2 / 9 | |
| 2.6.0 | 2 / 9 | |
| 2.5.0 | 2 / 9 | |
| 2.4.0 | 2 / 9 | |
| 2.3.0 | 2 / 9 | |
| 2.2.0 | 2 / 9 | |
| 2.1.0 | 2 / 9 | |
| 2.0.0 | 2 / 9 |
v2.72.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.72.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.71.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.70.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.69.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.68.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.67.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.66.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.66.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.65.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.64.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.63.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.63.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.63.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.62.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.62.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.62.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.61.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.61.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.60.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.59.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.58.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.58.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.57.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.56.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.56.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.55.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.55.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.54.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.53.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.52.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.52.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.51.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.51.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.50.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.49.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.49.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.48.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.47.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.46.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.44.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.43.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.42.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.41.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.40.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.39.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.39.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.38.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.38.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.37.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.34.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.34.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.32.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.31.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.31.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.29.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.28.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.24.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.3.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.1.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.