← Home

@lark-apaas/fullstack-cli

npm

CLI tool for fullstack template management

21
Versions
MIT
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

bytednpmfengtianran_bytedxiaochuanzhang_bytedbyted.lycoirefduanlikang_bytechengshihao1yanmingjiangprgrmr_byte

Keywords

fullstackclitemplate

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:child-process-import AI (semgrep): CLI tool that scaffolds and runs dev processes; child_process is expected and documented usage. ai
semgrep semgrep:env-spread AI (semgrep): Spreading process.env into a child process spawn call is standard practice for CLI dev scripts. ai
phantom-deps phantom-dep:shadcn AI (phantom-deps): shadcn is a CLI tool dependency referenced in config/template files, not directly imported in JS. ai
phantom-deps phantom-dep:zod-to-json-schema AI (phantom-deps): Used in generated/config files rather than direct imports; stable false positive for this package. ai

Versions (showing 21 of 21)

Version Deps Published
1.1.41 15 / 5
1.1.40 15 / 5
1.1.20 11 / 4
1.1.19 11 / 4
1.1.18 11 / 4
1.1.17 11 / 4
1.1.16 11 / 4
1.1.14 11 / 4
1.1.13 11 / 4
1.1.7 5 / 3
1.1.4 5 / 2
1.1.3 5 / 2
1.1.2 5 / 2
1.1.1 5 / 2
1.1.0 5 / 2
1.0.6 5 / 2
1.0.5 5 / 2
1.0.4 5 / 2
1.0.3 5 / 2
1.0.1 5 / 2
1.0.0 4 / 2

v1.1.41

2 findings
HIGH env-spread: templates/scripts/dev.js:122 semgrep

Spreading entire process.env into an object — may capture all secrets 120 | shell: true, 121 | cwd: PROJECT_ROOT, > 122 | env: { ...process.env }, 123 | }); 124 |

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.

v1.1.40

2 findings
HIGH env-spread: templates/scripts/dev.js:122 semgrep

Spreading entire process.env into an object — may capture all secrets 120 | shell: true, 121 | cwd: PROJECT_ROOT, > 122 | env: { ...process.env }, 123 | }); 124 |

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.

v1.1.20

1 finding
LOW No provenance attestation provenance

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

v1.1.19

1 finding
LOW No provenance attestation provenance

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

v1.1.18

1 finding
LOW No provenance attestation provenance

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

v1.1.17

1 finding
LOW No provenance attestation provenance

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

v1.1.16

1 finding
LOW No provenance attestation provenance

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

v1.1.14

1 finding
LOW No provenance attestation provenance

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

v1.1.13

1 finding
LOW No provenance attestation provenance

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

v1.1.7

1 finding
LOW No provenance attestation provenance

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

v1.1.4

1 finding
LOW No provenance attestation provenance

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

v1.1.3

1 finding
LOW No provenance attestation provenance

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

v1.1.2

1 finding
LOW No provenance attestation provenance

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

v1.1.1

1 finding
LOW No provenance attestation provenance

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

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.0.6

1 finding
LOW No provenance attestation provenance

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

v1.0.5

1 finding
LOW No provenance attestation provenance

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

v1.0.4

1 finding
LOW No provenance attestation provenance

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

v1.0.3

1 finding
LOW No provenance attestation provenance

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

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

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