@veloxts/cli MIT 27 versions

@veloxts/cli

npm Repository Homepage

Developer tooling and CLI commands for VeloxTS framework

27

Versions

MIT

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

zzal

Keywords

veloxclidevmigratetypescript

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:hot-hook	AI (phantom-deps): hot-hook used via config (e.g. velox config file), not direct import; consistent with HMR tooling integration.	ai	2026/05/02
dependencies	unvetted-dep:hot-hook	AI (dependencies): hot-hook is a known ESM hot-reload utility; legitimate use in a CLI/dev-tooling package.	ai	2026/05/02
phantom-deps	phantom-dep:@veloxts/auth	AI (phantom-deps): Same-org monorepo dependency; indirectly used through framework exports.	ai	2026/05/02
phantom-deps	phantom-dep:@veloxts/orm	AI (phantom-deps): Same-org monorepo dependency; indirectly used through framework exports.	ai	2026/05/02
phantom-deps	phantom-dep:@veloxts/core	AI (phantom-deps): Same-org monorepo dependency; indirectly used through framework exports.	ai	2026/05/02
phantom-deps	phantom-dep:@veloxts/router	AI (phantom-deps): Same-org monorepo dependency; indirectly used through framework exports.	ai	2026/05/02
phantom-deps	phantom-dep:tsx	AI (phantom-deps): tsx is a runtime dep used via CLI invocation, not direct import; stable false positive for this package.	ai	2026/04/28
typosquat	typosquat.levenshtein:joi	AI (typosquat): @veloxts/cli is a scoped framework CLI package; Levenshtein match to 'joi' is a false positive.	ai	2026/04/28
phantom-deps	phantom-dep:@veloxts/validation	AI (phantom-deps): Same-org peer dep; likely used indirectly through framework integration, stable false positive.	ai	2026/04/28

Versions (showing 27 of 27)

Version	Deps	Published
0.8.3	14 / 8	2026-04-25
0.8.2	14 / 8	2026-04-25
0.7.5	14 / 8	2026-02-16
0.6.101	14 / 8	2026-02-09
0.6.89	14 / 8	2026-01-31
0.6.86	14 / 8	2026-01-28
0.6.70	13 / 8	2026-01-06
0.6.67	13 / 8	2026-01-05
0.6.65	13 / 8	2026-01-04
0.6.64	13 / 8	2026-01-04
0.6.57	13 / 8	2026-01-02
0.6.51	13 / 8	2025-12-30
0.4.7	11 / 6	2025-12-11
0.4.3	10 / 6	2025-12-09
0.4.2	10 / 6	2025-12-08
0.4.1	10 / 6	2025-12-08
0.4.0	9 / 2	2025-12-08
0.3.6	9 / 2	2025-12-08
0.3.5	9 / 2	2025-12-07
0.3.4	9 / 2	2025-12-07
0.3.3	9 / 2	2025-12-06
0.3.2	9 / 2	2025-12-05
0.3.1	9 / 2	2025-12-05
0.3.0	9 / 2	2025-12-05
0.2.2	9 / 2	2025-12-05
0.2.0	9 / 2	2025-12-05
0.1.0	9 / 2	2025-12-04

v0.8.3

1 finding

LOW No provenance attestation provenance

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

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

v0.6.101

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

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

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

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

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

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

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

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

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

v0.4.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.4.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.4.1

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.4.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.3.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.

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

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

v0.3.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.3.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.3.1

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.3.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.2.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.2.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.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.