@aws-cdk/aws-sns
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
awscdkconstructssns
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:aws-sdk | AI (typosquat): False positive: @aws-cdk/aws-sns is a scoped package under the official @aws-cdk namespace, not a typosquat of aws-sdk. This naming pattern is consistent across all 288 versions of this package. | ai | |
| phantom-deps | phantom-dep:@aws-cdk/aws-events | AI (phantom-deps): Same-org sibling CDK package; phantom dep finding is a false positive for CDK construct libraries that use peer deps for type-only references. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 1.204.0 | 8 / 8 |
v1.204.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.