← Home

@digigov/cli

npm
19
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

kpaptsironisvkefallinos.grnetthanasisk00sotirangelo

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped CLI package @digigov/cli has no relation to joi; Levenshtein match is coincidental. ai
semgrep semgrep:child-process-import AI (semgrep): CLI tool legitimately uses execSync to run build/project commands; stable pattern for this package. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require loads user-provided digigovrc.js config file; intentional plugin/config pattern for this CLI. ai

Versions (showing 19 of 19)

Version Deps Published
2.5.0 7 / 4
2.4.2 7 / 4
2.4.1 7 / 4
2.4.0 7 / 4
2.3.0 7 / 4
2.2.3 5 / 4
2.2.1 5 / 4
2.2.0 5 / 4
2.1.1 5 / 4
2.1.0 5 / 4
2.0.14 5 / 4
2.0.13 5 / 4
2.0.12 5 / 4
2.0.11 5 / 4
2.0.10 5 / 4
2.0.9 5 / 4
2.0.6 6 / 4
2.0.4 6 / 4
2.0.2 6 / 4

v2.5.0

1 finding
LOW No provenance attestation provenance

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

v2.0.2

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.