@aws-crypto/kms-keyring-node
3
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a declared runtime dep used implicitly by TypeScript compiled output; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/client-dynamodb | AI (phantom-deps): Declared runtime dep for branch keystore; loaded by convention, not a direct import in this module. | ai |
v4.2.4
2 findings
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.
INFO
Publisher changed: aws-crypto-tools-ci-bot → GitHub Actions (on unknown date, now via trusted publisher with provenance)
provenance
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (aws-crypto-tools-ci-bot) on unknown date, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.