@datocms/cma-client
JS client for DatoCMS REST Content Management API
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Standard binary decode helper in id.ts; not obfuscation or payload hiding. | ai | |
| dependencies | unvetted-dep:@datocms/rest-client-utils | AI (dependencies): Sibling package in the same DatoCMS monorepo; stable false positive for this package. | ai |
Versions (showing 51 of 63)
| Version | Deps | Published |
|---|---|---|
| 5.6.0 | 3 / 1 | |
| 5.5.5 | 3 / 1 | |
| 5.5.4 | 3 / 1 | |
| 5.5.3 | 3 / 1 | |
| 5.5.1 | 3 / 1 | |
| 5.5.0 | 3 / 1 | |
| 5.4.22 | 3 / 1 | |
| 5.4.21 | 3 / 2 | |
| 5.4.20 | 3 / 2 | |
| 5.4.17 | 3 / 2 | |
| 5.4.16 | 3 / 2 | |
| 5.4.15 | 3 / 2 | |
| 5.4.14 | 3 / 2 | |
| 5.4.13 | 3 / 2 | |
| 5.4.12 | 3 / 2 | |
| 5.4.11 | 3 / 2 | |
| 5.4.10 | 3 / 2 | |
| 5.4.9 | 3 / 2 | |
| 5.4.7 | 3 / 2 | |
| 5.4.6 | 3 / 2 | |
| 5.4.5 | 3 / 2 | |
| 5.4.4 | 3 / 2 | |
| 5.4.3 | 3 / 2 | |
| 5.4.2 | 3 / 2 | |
| 5.4.1 | 3 / 2 | |
| 5.4.0 | 3 / 2 | |
| 5.2.8 | 3 / 2 | |
| 5.2.5 | 3 / 2 | |
| 5.2.1 | 3 / 2 | |
| 5.2.0 | 3 / 2 | |
| 5.1.30 | 3 / 2 | |
| 5.1.29 | 3 / 2 | |
| 5.1.28 | 3 / 2 | |
| 5.1.27 | 3 / 2 | |
| 5.1.26 | 3 / 2 | |
| 5.1.25 | 3 / 2 | |
| 5.1.24 | 3 / 2 | |
| 5.1.23 | 3 / 2 | |
| 5.1.22 | 3 / 2 | |
| 5.1.21 | 3 / 2 | |
| 5.1.20 | 3 / 2 | |
| 5.1.19 | 3 / 2 | |
| 5.1.18 | 3 / 2 | |
| 5.1.17 | 3 / 2 | |
| 5.1.16 | 3 / 2 | |
| 5.1.15 | 3 / 2 | |
| 5.1.14 | 3 / 2 | |
| 5.1.13 | 3 / 2 | |
| 5.1.12 | 3 / 2 | |
| 5.1.11 | 3 / 2 | |
| 5.1.10 | 3 / 2 |
v5.6.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sistrall_) than the most recent previously approved version (stefanoverna) on unknown date, but sistrall_ is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.5.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sistrall_) than the most recent previously approved version (stefanoverna) on unknown date, but sistrall_ is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.5.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (stefanoverna) than the most recent previously approved version (souljuse) on 2026-06-29, but stefanoverna is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.