@aws-cdk/aws-sns-subscriptions
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:constructs | AI (phantom-deps): constructs is a standard peer/transitive dep in all CDK v1 packages; not directly imported but legitimately declared. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@aws-cdk/aws-kms | AI (phantom-deps): @aws-cdk/aws-kms is a sibling CDK package used as a peer dep for KMS key types in SNS subscriptions; phantom detection is a false positive for CDK's peer dep pattern. | ai |
Versions (showing 24 of 224)
| Version | Deps | Published |
|---|---|---|
| 1.32.1 | 6 / 6 | |
| 1.32.0 | 6 / 6 | |
| 1.31.0 | 6 / 6 | |
| 1.30.0 | 6 / 6 | |
| 1.29.0 | 6 / 6 | |
| 1.28.0 | 5 / 6 | |
| 1.27.0 | 5 / 6 | |
| 1.26.0 | 5 / 6 | |
| 1.25.0 | 5 / 6 | |
| 1.24.0 | 5 / 6 | |
| 1.23.0 | 5 / 6 | |
| 1.22.0 | 5 / 6 | |
| 1.21.1 | 5 / 6 | |
| 1.21.0 | 5 / 6 | |
| 1.20.0 | 5 / 6 | |
| 1.19.0 | 5 / 6 | |
| 1.18.0 | 5 / 6 | |
| 1.17.1 | 5 / 6 | |
| 1.17.0 | 5 / 6 | |
| 1.16.3 | 5 / 6 | |
| 1.16.2 | 5 / 6 | |
| 1.16.1 | 5 / 6 | |
| 1.16.0 | 5 / 6 | |
| 1.0.0 | 5 / 6 |
v1.32.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.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.