@digigov/cli-app BSD-2-Clause 19 versions

@digigov/cli-app

npm

@digigov developer cli tool

19

Versions

BSD-2-Clause

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

kpaptsironisvkefallinos.grnetthanasisk00sotirangelo

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
semgrep	semgrep:dynamic-require	AI (semgrep): Loads project-local next.config.js via path.join — standard Next.js CLI pattern, stable across versions.	ai	2026/05/15
phantom-deps	phantom-dep:publint	AI (phantom-deps): Used as a dev/scripts tool, not imported at runtime; stable false positive for this package.	ai	2026/05/15
phantom-deps	phantom-dep:url-loader	AI (phantom-deps): Referenced in build config files, not directly imported; expected pattern for CLI build tooling.	ai	2026/05/15
phantom-deps	phantom-dep:babel-loader	AI (phantom-deps): Referenced in build config files, not directly imported; expected pattern for CLI build tooling.	ai	2026/05/15
phantom-deps	phantom-dep:@digigov/cli-build	AI (phantom-deps): Same-org dependency used indirectly via CLI toolchain; stable false positive.	ai	2026/05/15

Versions (showing 19 of 19)

Version	Deps	Published
2.3.0	10 / 5	2026-06-04
2.2.3	10 / 5	2026-05-28
2.2.1	10 / 5	2026-05-15
2.2.0	10 / 5	2026-05-14
2.1.1	10 / 5	2026-05-04
2.1.0	10 / 5	2026-04-08
2.0.14	10 / 5	2026-04-02
2.0.13	10 / 5	2026-03-31
2.0.12	10 / 5	2026-03-23
2.0.11	10 / 5	2026-03-09
2.0.10	10 / 5	2026-03-05
2.0.9	10 / 5	2026-03-05
2.0.8	10 / 5	2026-02-11
2.0.7	10 / 5	2026-02-10
2.0.6	10 / 5	2026-01-28
2.0.5	10 / 5	2026-01-27
2.0.4	10 / 5	2026-01-27
2.0.3	10 / 5	2026-01-21
2.0.2	10 / 5	2026-01-21

v2.3.0

1 finding

LOW No provenance attestation provenance

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

v2.2.3

1 finding

LOW No provenance attestation provenance

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

v2.2.1

1 finding

LOW No provenance attestation provenance

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

v2.2.0

1 finding

LOW No provenance attestation provenance

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

v2.1.1

1 finding

LOW No provenance attestation provenance

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

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

v2.0.14

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.

v2.0.13

1 finding

LOW No provenance attestation provenance

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

v2.0.12

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.

v2.0.11

1 finding

LOW No provenance attestation provenance

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

v2.0.10

1 finding

LOW No provenance attestation provenance

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

v2.0.9

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.

v2.0.8

1 finding

LOW No provenance attestation provenance

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

v2.0.7

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.

v2.0.6

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.

v2.0.5

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.

v2.0.4

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.

v2.0.3

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.

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.