@datocms/cma-client-node
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Signals triggered by unrelated maintainer 'datoroger'; this is the official DatoCMS package with 194 versions and a verified GitHub repo. | ai |
Versions (showing 62 of 62)
| Version | Deps | Published |
|---|---|---|
| 5.5.5 | 4 / 6 | |
| 5.5.4 | 4 / 6 | |
| 5.5.3 | 4 / 6 | |
| 5.5.1 | 4 / 6 | |
| 5.5.0 | 4 / 6 | |
| 5.4.22 | 4 / 6 | |
| 5.4.21 | 4 / 6 | |
| 5.4.20 | 4 / 6 | |
| 5.4.17 | 4 / 6 | |
| 5.4.16 | 4 / 6 | |
| 5.4.15 | 4 / 6 | |
| 5.4.14 | 4 / 6 | |
| 5.4.13 | 4 / 6 | |
| 5.4.12 | 4 / 6 | |
| 5.4.11 | 4 / 6 | |
| 5.4.10 | 4 / 6 | |
| 5.4.9 | 4 / 6 | |
| 5.4.8 | 4 / 6 | |
| 5.4.7 | 4 / 6 | |
| 5.4.6 | 4 / 6 | |
| 5.4.5 | 4 / 6 | |
| 5.4.4 | 4 / 6 | |
| 5.4.3 | 4 / 6 | |
| 5.4.2 | 4 / 6 | |
| 5.4.1 | 4 / 6 | |
| 5.4.0 | 4 / 6 | |
| 5.2.8 | 4 / 6 | |
| 5.2.5 | 4 / 6 | |
| 5.2.3 | 4 / 6 | |
| 5.2.1 | 4 / 6 | |
| 5.1.29 | 4 / 6 | |
| 5.1.28 | 4 / 6 | |
| 5.1.27 | 4 / 6 | |
| 5.1.26 | 4 / 6 | |
| 5.1.25 | 4 / 6 | |
| 5.1.24 | 4 / 6 | |
| 5.1.23 | 4 / 6 | |
| 5.1.22 | 4 / 6 | |
| 5.1.21 | 4 / 6 | |
| 5.1.20 | 4 / 6 | |
| 5.1.19 | 4 / 6 | |
| 5.1.18 | 4 / 6 | |
| 5.1.17 | 4 / 6 | |
| 5.1.16 | 4 / 6 | |
| 5.1.15 | 4 / 6 | |
| 5.1.14 | 4 / 6 | |
| 5.1.13 | 4 / 6 | |
| 5.1.12 | 4 / 6 | |
| 5.1.11 | 4 / 6 | |
| 5.1.10 | 4 / 6 | |
| 5.1.9 | 4 / 6 | |
| 5.1.8 | 4 / 6 | |
| 5.1.7 | 4 / 6 | |
| 5.1.6 | 4 / 6 | |
| 5.1.5 | 4 / 6 | |
| 5.1.4 | 4 / 6 | |
| 5.1.3 | 4 / 6 | |
| 5.1.2 | 4 / 6 | |
| 5.1.1 | 4 / 6 | |
| 5.1.0 | 4 / 6 | |
| 5.0.1 | 4 / 6 | |
| 5.0.0 | 4 / 6 |
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 2026-07-21, 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.