← Home

@vue-skuilder/cli

npm

CLI scaffolding tool for vue-skuilder projects

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

Maintainers

nilock

Keywords

cliscaffoldingvueskuildereducationcourse

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@vue-skuilder/standalone-ui AI (phantom-deps): Same-org sibling dep; may be used indirectly via CLI scaffolding logic rather than direct import. ai
semgrep semgrep:env-spread AI (semgrep): Pattern is passing env to a child process with a single override; not exfiltration. Stable for this CLI package. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped monorepo package @vue-skuilder/cli; no meaningful similarity to 'joi'. False positive. ai
phantom-deps phantom-dep:leveldown AI (phantom-deps): leveldown is a declared runtime dep used transitively via pouchdb; phantom-dep heuristic misfires here. ai

Versions (showing 22 of 22)

Version Deps Published
0.2.5 19 / 11
0.2.4 19 / 11
0.2.3 19 / 11
0.2.2 19 / 11
0.2.1 19 / 11
0.2.0 19 / 11
0.1.40 19 / 11
0.1.39 19 / 11
0.1.38 19 / 11
0.1.36 19 / 11
0.1.35 19 / 11
0.1.14 19 / 11
0.1.13 19 / 9
0.1.12 19 / 9
0.1.11 19 / 9
0.1.10 17 / 10
0.1.9 18 / 10
0.1.8 18 / 10
0.1.6 7 / 4
0.1.5 7 / 4
0.1.4 5 / 4
0.1.3 5 / 4

v0.2.5

1 finding
LOW No provenance attestation provenance

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

v0.2.4

1 finding
LOW No provenance attestation provenance

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

v0.2.3

1 finding
LOW No provenance attestation provenance

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

v0.2.2

1 finding
LOW No provenance attestation provenance

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

v0.2.1

1 finding
LOW No provenance attestation provenance

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

v0.2.0

1 finding
LOW No provenance attestation provenance

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

v0.1.40

1 finding
LOW No provenance attestation provenance

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

v0.1.39

1 finding
LOW No provenance attestation provenance

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

v0.1.38

1 finding
LOW No provenance attestation provenance

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

v0.1.36

1 finding
LOW No provenance attestation provenance

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

v0.1.35

2 findings
HIGH env-spread: src/commands/studio.ts:1028 semgrep

Spreading entire process.env into an object — may capture all secrets 1026 | cwd: coursePath, 1027 | stdio: 'pipe', > 1028 | env: { ...process.env, BUILD_MODE: 'library' }, 1029 | }); 1030 |

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

2 findings
HIGH env-spread: src/commands/studio.ts:975 semgrep

Spreading entire process.env into an object — may capture all secrets 973 | cwd: coursePath, 974 | stdio: 'pipe', > 975 | env: { ...process.env, BUILD_MODE: 'library' }, 976 | }); 977 |

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

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

v0.1.11

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

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

v0.1.8

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