@valbuild/cli No license 34 versions

@valbuild/cli

npm Repository Homepage

Val CLI tools

34

Versions

—

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

freekhtheodorc_blank

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Package migrated to GitHub Actions CI publishing with SLSA attestation; consistent with org-level automation adoption.	ai	2026/05/30
provenance	missing-githead	AI (provenance): SLSA provenance attestation present; gitHead absence is superseded by Sigstore attestation for this package.	ai	2026/05/26
phantom-deps	phantom-dep:express	AI (phantom-deps): CLI tool uses express as a runtime server dep; dynamic import pattern is expected for this package.	ai	2026/05/17
phantom-deps	phantom-dep:@inquirer/confirm	AI (phantom-deps): CLI tool uses inquirer packages for interactive prompts; phantom detection is a false positive here.	ai	2026/05/17
phantom-deps	phantom-dep:@inquirer/prompts	AI (phantom-deps): CLI tool uses inquirer packages for interactive prompts; phantom detection is a false positive here.	ai	2026/05/17
dependencies	unvetted-dep:@valbuild/eslint-plugin	AI (dependencies): Same-org monorepo sibling dependency; consistently co-published with this package across versions.	ai	2026/05/17
typosquat	typosquat.levenshtein:joi	AI (typosquat): @valbuild/cli is a scoped monorepo package; Levenshtein match to 'joi' is a false positive.	ai	2026/04/29
phantom-deps	phantom-dep:open	AI (phantom-deps): open is a declared runtime dep; phantom-dep heuristic misfires on indirect usage patterns.	ai	2026/04/29
phantom-deps	phantom-dep:cors	AI (phantom-deps): cors is a declared runtime dep in a CLI tool; phantom-dep heuristic misfires on indirect usage patterns.	ai	2026/04/29
phantom-deps	phantom-dep:@valbuild/eslint-plugin	AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic not meaningful for monorepo tooling packages.	ai	2026/04/29

Versions (showing 34 of 134)

Version	Deps	Published
0.43.0	7 / 0	2023-12-07
0.42.0	7 / 0	2023-12-06
0.41.0	7 / 0	2023-12-06
0.40.0	7 / 0	2023-12-04
0.39.0	7 / 0	2023-12-04
0.38.0	7 / 0	2023-12-04
0.37.0	7 / 0	2023-11-30
0.36.0	7 / 0	2023-11-30
0.35.0	7 / 0	2023-11-30
0.34.0	7 / 0	2023-11-21
0.33.0	7 / 0	2023-11-21
0.32.0	7 / 0	2023-11-21
0.31.0	7 / 0	2023-11-20
0.30.0	7 / 0	2023-11-17
0.29.0	7 / 0	2023-11-17
0.28.0	7 / 0	2023-11-15
0.27.0	7 / 0	2023-11-14
0.26.0	7 / 0	2023-11-14
0.25.0	7 / 0	2023-11-14
0.24.0	7 / 0	2023-11-13
0.23.0	7 / 0	2023-11-13
0.22.0	7 / 0	2023-11-10
0.21.0	7 / 0	2023-10-24
0.20.2	7 / 0	2023-10-16
0.20.0	7 / 0	2023-10-13
0.19.0	7 / 0	2023-10-13
0.18.0	7 / 0	2023-09-21
0.17.0	7 / 0	2023-09-20
0.16.0	7 / 0	2023-08-25
0.15.0	5 / 0	2023-08-16
0.14.0	5 / 0	2023-08-16
0.13.3	5 / 0	2023-06-13
0.13.0	5 / 0	2023-06-01
0.12.0	5 / 0	2023-06-01

v0.43.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.

v0.42.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.

v0.41.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.

v0.40.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.

v0.39.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.

v0.38.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.

v0.37.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.

v0.36.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.

v0.35.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.

v0.34.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.

v0.33.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.

v0.32.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.

v0.31.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.

v0.30.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.

v0.29.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.

v0.28.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.

v0.27.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.

v0.26.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.

v0.25.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.

v0.24.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.

v0.23.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.

v0.22.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.

v0.21.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.

v0.20.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.

v0.20.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.

v0.19.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.

v0.18.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.

v0.17.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.

v0.16.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.

v0.15.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.

v0.14.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.

v0.13.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.

v0.13.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.

v0.12.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.