← Home

datocms

npm Repository Homepage

CLI to interact with DatoCMS APIs

17
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

stefanoverna

Keywords

datocmscli

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:env-spread AI (semgrep): Spreading process.env to pass API token to child runner process is standard CLI behavior for this package. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require loads user-specified CMA resource path; expected pattern for a CLI tool. ai
phantom-deps phantom-dep:@oclif/plugin-help AI (phantom-deps): oclif plugins are declared in oclif config section, not imported directly; stable false positive. ai
phantom-deps phantom-dep:@oclif/plugin-plugins AI (phantom-deps): oclif plugins are declared in oclif config section, not imported directly; stable false positive. ai
phantom-deps phantom-dep:@oclif/plugin-not-found AI (phantom-deps): oclif plugins are declared in oclif config section, not imported directly; stable false positive. ai
phantom-deps phantom-dep:@oclif/plugin-autocomplete AI (phantom-deps): oclif plugins are declared in oclif config section, not imported directly; stable false positive. ai
phantom-deps phantom-dep:@oclif/plugin-warn-if-update-available AI (phantom-deps): oclif plugins are declared in oclif config section, not imported directly; stable false positive. ai

Versions (showing 17 of 17)

Version Deps Published
4.0.27 21 / 5
4.0.26 21 / 5
4.0.25 21 / 5
4.0.24 21 / 5
4.0.23 21 / 5
4.0.22 21 / 5
4.0.21 20 / 5
4.0.20 20 / 5
4.0.19 19 / 5
4.0.18 19 / 5
4.0.17 19 / 5
4.0.16 19 / 5
4.0.15 19 / 5
4.0.14 19 / 5
4.0.13 19 / 5
4.0.12 18 / 5
4.0.11 1 / 0

v4.0.27

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.26

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.25

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.24

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.21

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.20

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.19

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.18

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.17

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.16

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.15

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.14

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.13

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.11

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.