@dcl/sns-component
AWS SNS component for core components library
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions publisher with SLSA attestation; consistent with Decentraland org CI/CD migration. | ai | |
| provenance | no-provenance | AI (provenance): Decentraland bot publisher; no provenance is consistent across all their packages and not a risk indicator here. | ai | |
| phantom-deps | phantom-dep:@dcl/core-commons | AI (phantom-deps): Same-org dependency; declared but may be re-exported rather than directly imported — stable false positive for this package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 3.1.2 | 3 / 1 | |
| 3.1.1 | 3 / 1 | |
| 3.1.0 | 3 / 1 | |
| 3.0.2 | 3 / 1 | |
| 3.0.1 | 3 / 1 | |
| 3.0.0 | 3 / 1 |
v3.1.2
2 findingsThis version was published by a different npm account than previous versions on 2026-05-26. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.