@aws-cdk/cfnspec Apache-2.0 51 versions

@aws-cdk/cfnspec

npm Repository Homepage

The CloudFormation resource specification used by @aws-cdk packages

51

Versions

Apache-2.0

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

romainmulleramzn-ossrix0rrraws-cdk-team

Keywords

awscdk

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	2026/04/24
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	2026/04/24
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	2026/04/24
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	2026/04/23

Versions (showing 51 of 388)

Show 1 prerelease View all versions

Version	Deps	Published
2.72.1	2 / 9	2023-03-31
2.72.0	2 / 9	2023-03-29
2.71.0	2 / 9	2023-03-29
2.70.0	2 / 9	2023-03-22
2.69.0	2 / 9	2023-03-14
2.68.0	2 / 9	2023-03-08
2.67.0	2 / 9	2023-03-02
2.66.1	2 / 9	2023-02-24
2.66.0	2 / 9	2023-02-21
2.65.0	2 / 9	2023-02-15
2.64.0	2 / 9	2023-02-09
2.63.2	2 / 9	2023-02-04
2.63.1	2 / 9	2023-02-03
2.63.0	2 / 9	2023-01-31
2.62.2	2 / 9	2023-01-27
2.62.1	2 / 9	2023-01-26
2.62.0	2 / 9	2023-01-25
2.61.1	2 / 9	2023-01-20
2.61.0	2 / 9	2023-01-19
2.60.0	2 / 9	2023-01-12
2.59.0	2 / 9	2023-01-03
2.58.1	2 / 9	2022-12-30
2.58.0	2 / 9	2022-12-29
2.57.0	2 / 9	2022-12-27
2.56.1	2 / 9	2022-12-23
2.56.0	2 / 9	2022-12-21
2.55.1	2 / 9	2022-12-16
2.55.0	2 / 9	2022-12-14
2.54.0	2 / 9	2022-12-07
2.53.0	2 / 9	2022-11-29
2.52.1	2 / 9	2022-11-29
2.52.0	2 / 9	2022-11-27
2.51.1	2 / 9	2022-11-18
2.51.0	2 / 9	2022-11-18
2.50.0	2 / 9	2022-11-01
2.49.1	2 / 9	2022-11-01
2.49.0	2 / 9	2022-10-28
2.48.0	2 / 9	2022-10-27
2.47.0	2 / 9	2022-10-20
2.46.0	2 / 9	2022-10-13
2.45.0	2 / 9	2022-10-06
2.44.0	2 / 9	2022-09-29
2.43.1	2 / 9	2022-09-23
2.43.0	2 / 9	2022-09-21
2.42.1	2 / 9	2022-09-19
2.42.0	2 / 9	2022-09-16
2.41.0	2 / 9	2022-09-08
2.40.0	2 / 9	2022-09-01
2.39.1	2 / 9	2022-08-29
2.39.0	2 / 9	2022-08-25
2.38.1	2 / 9	2022-08-18

v2.72.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.72.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.71.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.70.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.69.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.68.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.67.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.66.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.66.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.65.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.64.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.63.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.63.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.63.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.62.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.62.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.62.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.61.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.61.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.60.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.59.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.58.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.58.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.57.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.56.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.56.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.55.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.55.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.54.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.53.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.52.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.52.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.51.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.51.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.50.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.49.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.49.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.48.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.47.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.46.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.45.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.44.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.43.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.43.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.42.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.42.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.41.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.40.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.39.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.39.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.38.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.