← Home

@aws-crypto/raw-aes-keyring-node

npm Repository Homepage
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.

SourceRuleReasonAccepted byWhen
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

Versions (showing 3 of 3)

Version Deps Published
5.0.0 4 / 0
4.2.4 4 / 0
4.2.2 4 / 0

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.