@aws-cdk/core
1
Versions
—
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
awscdkjsiicdk-core
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @aws-cdk/core is the canonical AWS CDK core library from Amazon Web Services, not a typosquat of 'cors'. The name match is a false positive due to string similarity. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process is used in bundling.js for legitimate Docker/asset bundling operations, which is core CDK functionality for infrastructure tooling. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require() in the custom resource provider entrypoint is intentional — it loads user-supplied Lambda handler modules at runtime, a documented CDK custom resource pattern. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 1.204.0 | 8 / 15 |
v1.204.0
2 findings
HIGH
typosquat.levenshtein: Possible typosquat of 'cors'
typosquat
Package name '@aws-cdk/core' is 1 edit(s) away from popular package 'cors'.
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.