@aws-crypto/raw-aes-keyring-node
2
Versions
—
License
No
Install Scripts
Verified
Provenance
Supply chain provenance
Status for the latest visible version.
SLSA provenance attestation
npm registry signatures
gitHead linked
Maintainers
amzn-ossaws-crypto-tools-ci-bot
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| email-domain | unclaimed-email:amazon.coms | AI (email-domain): Typo in package.json author email (amazon.coms vs amazon.com); SLSA provenance confirms legitimate AWS CI/CD publish pipeline. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit TypeScript runtime dep; stable false positive for compiled TS packages. | ai |
v5.0.0
2 findings
HIGH
Unclaimed maintainer email domain: amazon.coms
email-domain
Maintainer email '[email protected]' uses domain 'amazon.coms' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
INFO
Has SLSA provenance attestation
provenance
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.2
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.