← Home

@lark-apaas/miaoda-cli

npm

Miaoda 平台命令行工具，面向 Agent 调用

16
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

bytednpmfengtianran_bytedxiaochuanzhang_bytedbyted.lycoirefduanlikang_byte

Keywords

miaodacliagent

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:env-spread AI (semgrep): Fires inside a scaffolded project template (upgrade/templates/), not CLI runtime code; expected pattern for dev scripts. ai
semgrep semgrep:child-process-import AI (semgrep): child_process used in a template dev.js scaffold file, not in the CLI's own execution path. ai

Versions (showing 16 of 16)

Version Deps Published
0.1.15 5 / 16
0.1.14 5 / 16
0.1.13 5 / 16
0.1.12 5 / 16
0.1.11 5 / 16
0.1.10 5 / 16
0.1.9 5 / 16
0.1.8 5 / 16
0.1.7 5 / 16
0.1.6 4 / 16
0.1.5 4 / 16
0.1.4 4 / 16
0.1.3 4 / 16
0.1.2 3 / 16
0.1.1 2 / 11
0.1.0 2 / 11

v0.1.15

1 finding
LOW No provenance attestation provenance

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

v0.1.14

1 finding
LOW No provenance attestation provenance

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

v0.1.13

1 finding
LOW No provenance attestation provenance

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

v0.1.12

1 finding
LOW No provenance attestation provenance

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

v0.1.11

1 finding
LOW No provenance attestation provenance

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

v0.1.10

2 findings
HIGH env-spread: upgrade/templates/nestjs-react-fullstack/templates/scripts/dev.js:124 semgrep

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

LOW No provenance attestation provenance

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

v0.1.9

2 findings
HIGH env-spread: upgrade/templates/nestjs-react-fullstack/templates/scripts/dev.js:124 semgrep

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

LOW No provenance attestation provenance

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

v0.1.8

2 findings
HIGH env-spread: upgrade/templates/nestjs-react-fullstack/templates/scripts/dev.js:124 semgrep

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

LOW No provenance attestation provenance

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

v0.1.7

2 findings
HIGH env-spread: upgrade/templates/nestjs-react-fullstack/templates/scripts/dev.js:124 semgrep

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

LOW No provenance attestation provenance

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

v0.1.6

1 finding
LOW No provenance attestation provenance

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

v0.1.5

1 finding
LOW No provenance attestation provenance

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

v0.1.4

1 finding
LOW No provenance attestation provenance

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

v0.1.3

1 finding
LOW No provenance attestation provenance

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

v0.1.2

1 finding
LOW No provenance attestation provenance

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

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.