@datocms/cli-utils
Utils for DatoCMS CLI
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established DatoCMS package; lack of provenance is consistent across all versions and not a risk indicator here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Signal is from co-maintainer's other packages; this is a legitimate DatoCMS CLI utility with 18.6k weekly downloads. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 4.0.25 | 10 / 1 | |
| 4.0.23 | 10 / 1 | |
| 4.0.22 | 10 / 1 | |
| 4.0.21 | 10 / 1 | |
| 4.0.15 | 10 / 1 | |
| 4.0.14 | 10 / 1 | |
| 4.0.12 | 10 / 1 | |
| 4.0.6 | 10 / 1 | |
| 4.0.4 | 9 / 1 | |
| 4.0.2 | 9 / 1 | |
| 4.0.1 | 9 / 1 | |
| 4.0.0 | 9 / 1 | |
| 3.1.15 | 8 / 1 | |
| 3.1.14 | 8 / 1 | |
| 3.1.13 | 8 / 1 | |
| 3.1.12 | 8 / 1 | |
| 3.1.11 | 8 / 1 | |
| 3.1.10 | 8 / 1 | |
| 3.1.9 | 8 / 1 | |
| 3.1.8 | 8 / 1 | |
| 3.1.7 | 8 / 1 |
v4.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.