@riverbankcms/sdk
Riverbank CMS SDK for headless content consumption
3
Versions
MIT
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
riverbankcms
Keywords
headless-cmsriverbankcmscmscontentsdk
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@riverbankcms/api | AI (dependencies): Workspace-internal sibling package from same org; not an external unvetted dependency. | ai | |
| dependencies | unvetted-dep:@riverbankcms/blocks | AI (dependencies): Workspace-internal sibling package from same org; not an external unvetted dependency. | ai | |
| dependencies | unvetted-dep:@riverbankcms/site-renderer | AI (dependencies): Workspace-internal sibling package from same org; not an external unvetted dependency. | ai |
v0.55.0
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.
v0.2.0
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.
v0.1.0
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.