@cipherstash/protect-dynamodb
Protect.js DynamoDB Helpers
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): CipherStash org package; lack of provenance is consistent across their releases and not a risk indicator here. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 12.0.1 | 1 / 6 | |
| 11.0.2 | 1 / 6 | |
| 11.0.1 | 1 / 6 | |
| 11.0.0 | 1 / 6 | |
| 10.0.0 | 1 / 6 | |
| 9.0.0 | 1 / 6 | |
| 8.0.0 | 1 / 6 | |
| 7.0.0 | 1 / 6 | |
| 6.0.1 | 1 / 6 | |
| 6.0.0 | 1 / 6 | |
| 5.1.1 | 1 / 6 | |
| 5.1.0 | 1 / 6 | |
| 5.0.2 | 1 / 6 |
v12.0.1
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (cs-zcjbrewer) on 2026-07-08, 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.