← Home

@spaceflow/cli

npm Repository Homepage

Spaceflow CLI 工具

34
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

lydanne

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:env-spread AI (semgrep): Spreading process.env into a child_process spawn call is idiomatic; no exfiltration risk in this context. ai
semgrep semgrep:new-function-constructor AI (semgrep): Used solely to bypass rspack static analysis for a local file dynamic import; input is a controlled local dist path. ai
phantom-deps phantom-dep:@rspack/cli AI (phantom-deps): Listed as a runtime dependency and used via CLI invocation in build scripts, not a direct import. ai
phantom-deps phantom-dep:zod-to-json-schema AI (phantom-deps): Referenced in config files as documented; phantom-dep heuristic false positive for this package. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped package @spaceflow/cli is unrelated to joi; Levenshtein match is a false positive. ai

Versions (showing 34 of 34)

Version Deps Published
5.1.2 3 / 9
5.1.1 3 / 9
5.1.0 3 / 9
5.0.4 3 / 9
5.0.3 3 / 9
5.0.2 3 / 9
5.0.1 3 / 9
5.0.0 3 / 9
0.41.0 3 / 9
0.40.0 3 / 9
0.39.0 3 / 9
0.38.0 3 / 9
0.37.0 3 / 9
0.36.0 3 / 9
0.35.0 1 / 9
0.34.0 1 / 9
0.33.0 1 / 9
0.32.0 1 / 9
0.31.0 1 / 9
0.30.0 1 / 9
0.29.0 9 / 7
0.28.0 9 / 7
0.27.0 9 / 7
0.26.0 8 / 7
0.25.0 8 / 7
0.24.0 8 / 7
0.23.0 8 / 7
0.22.0 8 / 7
0.21.0 8 / 7
0.20.0 8 / 7
0.19.4 7 / 10
0.19.3 7 / 10
0.19.2 7 / 10
0.19.1 7 / 10

v5.1.2

1 finding
LOW No provenance attestation provenance

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

v5.1.1

1 finding
LOW No provenance attestation provenance

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

v5.1.0

1 finding
LOW No provenance attestation provenance

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

v5.0.3

1 finding
LOW No provenance attestation provenance

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

v5.0.2

1 finding
LOW No provenance attestation provenance

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

v5.0.1

1 finding
LOW No provenance attestation provenance

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

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

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. Consider requesting the maintainer enable provenance via CI/CD.

v0.39.0

1 finding
LOW No provenance attestation provenance

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

v0.38.0

1 finding
LOW No provenance attestation provenance

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

v0.37.0

1 finding
LOW No provenance attestation provenance

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

v0.36.0

1 finding
LOW No provenance attestation provenance

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

v0.35.0

1 finding
LOW No provenance attestation provenance

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

v0.34.0

1 finding
LOW No provenance attestation provenance

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

v0.33.0

1 finding
LOW No provenance attestation provenance

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

v0.32.0

1 finding
LOW No provenance attestation provenance

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

v0.31.0

1 finding
LOW No provenance attestation provenance

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

v0.30.0

1 finding
LOW No provenance attestation provenance

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

v0.29.0

1 finding
LOW No provenance attestation provenance

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

v0.28.0

1 finding
LOW No provenance attestation provenance

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

v0.27.0

1 finding
LOW No provenance attestation provenance

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

v0.26.0

1 finding
LOW No provenance attestation provenance

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

v0.25.0

1 finding
LOW No provenance attestation provenance

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

v0.24.0

1 finding
LOW No provenance attestation provenance

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

v0.23.0

1 finding
LOW No provenance attestation provenance

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

v0.22.0

1 finding
LOW No provenance attestation provenance

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

v0.21.0

1 finding
LOW No provenance attestation provenance

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

v0.20.0

1 finding
LOW No provenance attestation provenance

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

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

2 findings
HIGH env-spread: src/commands/mcp/mcp.command.ts:48 semgrep

Spreading entire process.env into an object — may capture all secrets 46 | stdio: "inherit", 47 | shell: true, > 48 | env: { ...process.env, MODELCONTEXT_PROTOCOL_INSPECTOR: "true" }, 49 | cwd: process.cwd(), 50 | },

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

2 findings
HIGH env-spread: src/commands/mcp/mcp.command.ts:48 semgrep

Spreading entire process.env into an object — may capture all secrets 46 | stdio: "inherit", 47 | shell: true, > 48 | env: { ...process.env, MODELCONTEXT_PROTOCOL_INSPECTOR: "true" }, 49 | cwd: process.cwd(), 50 | },

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.