@aws-cdk/custom-resources
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@aws-cdk/aws-stepfunctions-tasks | AI (dependencies): Same-org sibling CDK package, pinned exact version. | ai | |
| npm-metadata | url-dep:cdk-build-tools | AI (npm-metadata): Monorepo dev-tool file reference, standard for aws-cdk packages. | ai | |
| npm-metadata | url-dep:cfn2ts | AI (npm-metadata): Monorepo dev-tool file reference, standard for aws-cdk packages. | ai | |
| npm-metadata | url-dep:pkglint | AI (npm-metadata): Monorepo dev-tool file reference, standard for aws-cdk packages. | ai | |
| npm-metadata | url-dep:cdk-integ-tools | AI (npm-metadata): Monorepo dev-tool file reference, standard for aws-cdk packages. | ai | |
| source-diff | obfuscated-file:test/cdk.out/asset.5d5280180ad87e8a1c2a08423cb5b2dae41281832799cd51db5eff913091ade6/cfn-response.js | AI (source-diff): Transpiled test fixture asset, not real obfuscation or malicious code. | ai | |
| phantom-deps | phantom-dep:constructs | AI (phantom-deps): Used via CDK construct patterns, standard for this ecosystem. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process is used in the CDK custom resource Lambda runtime handler for legitimate SDK installation/invocation — standard pattern for this package. | ai | |
| semgrep | semgrep:http-module-request | AI (semgrep): HTTPS request is the required CloudFormation custom resource response mechanism (sending response to pre-signed S3 URL) — not exfiltration. | ai | |
| phantom-deps | phantom-dep:@aws-cdk/aws-sns | AI (phantom-deps): Same-org @aws-cdk scoped package; declared as dependency for type/construct usage, not a supply chain risk. | ai |
Versions (showing 19 of 219)
| Version | Deps | Published |
|---|---|---|
| 1.15.0 | 5 / 13 | |
| 1.14.0 | 5 / 13 | |
| 1.13.1 | 5 / 13 | |
| 1.13.0 | 5 / 13 | |
| 1.12.0 | 5 / 13 | |
| 1.11.0 | 5 / 13 | |
| 1.10.1 | 5 / 13 | |
| 1.10.0 | 5 / 13 | |
| 1.9.0 | 5 / 13 | |
| 1.8.0 | 5 / 14 | |
| 1.7.0 | 5 / 14 | |
| 1.6.1 | 5 / 14 | |
| 1.6.0 | 5 / 14 | |
| 1.5.0 | 5 / 14 | |
| 1.4.0 | 5 / 14 | |
| 1.3.0 | 5 / 14 | |
| 1.2.0 | 5 / 14 | |
| 1.1.0 | 5 / 14 | |
| 1.0.0 | 5 / 14 |
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.