← Home

@contentstack/cli-variants

npm
27
Versions
—
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

mynkcloudaccounts

Keywords

variant

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:dynamic-require AI (semgrep): Loads user-configured mock data path for testing; not an arbitrary code execution vector in this context. ai
phantom-deps phantom-dep:@oclif/core AI (phantom-deps): @oclif/core is referenced in oclif config blocks, not directly imported in source — stable false positive for oclif plugins. ai
phantom-deps phantom-dep:@oclif/plugin-help AI (phantom-deps): @oclif/plugin-help is a standard oclif config dependency, not directly imported — stable false positive for oclif plugins. ai

Versions (showing 27 of 27)

Version Deps Published
1.6.0 5 / 7
1.5.2 5 / 7
1.5.1 5 / 7
1.5.0 5 / 7
1.4.3 5 / 7
1.4.2 6 / 8
1.4.1 6 / 8
1.4.0 6 / 8
1.3.8 6 / 8
1.3.7 6 / 8
1.3.6 6 / 8
1.3.5 6 / 8
1.3.4 6 / 8
1.3.3 6 / 8
1.3.2 6 / 8
1.3.0 6 / 8
1.2.2 4 / 7
1.2.1 4 / 7
1.2.0 4 / 7
1.1.6 4 / 7
1.1.5 4 / 7
1.1.4 4 / 11
1.1.3 4 / 11
1.1.2 4 / 11
1.1.1 4 / 11
1.1.0 4 / 11
1.0.0 4 / 11

v1.6.0

1 finding
LOW No provenance attestation provenance

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

v1.5.2

1 finding
LOW No provenance attestation provenance

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

v1.2.0

1 finding
LOW No provenance attestation provenance

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

v1.1.6

1 finding
LOW No provenance attestation provenance

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

v1.1.5

1 finding
LOW No provenance attestation provenance

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

v1.1.4

1 finding
LOW No provenance attestation provenance

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

v1.1.3

1 finding
LOW No provenance attestation provenance

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

v1.1.2

1 finding
LOW No provenance attestation provenance

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

v1.1.1

1 finding
LOW No provenance attestation provenance

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

v1.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.

v1.0.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.