← Home

@yinuo-ngm/cli

npm

a CLI tool for Yinuo NG Manager

21
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

yinuobear

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@types/node AI (phantom-deps): Type-only package; not directly imported at runtime by convention. ai
semgrep semgrep:child-process-import AI (semgrep): CLI tool legitimately spawns server subprocess; child_process use is expected. ai
phantom-deps phantom-dep:execa AI (phantom-deps): execa is declared as a dependency; phantom-dep heuristic false positive for this package. ai
phantom-deps phantom-dep:env-paths AI (phantom-deps): env-paths is declared as a dependency; phantom-dep heuristic false positive for this package. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped package @yinuo-ngm/cli; Levenshtein match to 'joi' is a false positive with no brand impersonation. ai
semgrep semgrep:env-spread AI (semgrep): env-spread used to pass process.env to a child server process with an extra port override — standard pattern, not exfiltration. ai

Versions (showing 21 of 21)

Version Deps Published
0.1.20 8 / 0
0.1.19 8 / 0
0.1.18 8 / 0
0.1.17 7 / 0
0.1.16 7 / 0
0.1.15 7 / 0
0.1.14 7 / 0
0.1.13 7 / 0
0.1.12 7 / 0
0.1.11 7 / 0
0.1.10 6 / 0
0.1.9 6 / 0
0.1.8 6 / 0
0.1.7 6 / 0
0.1.6 6 / 0
0.1.5 6 / 0
0.1.4 6 / 0
0.1.3 7 / 0
0.1.2 7 / 0
0.1.1 7 / 0
0.1.0 7 / 0

v0.1.20

1 finding
LOW No provenance attestation provenance

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

v0.1.19

1 finding
LOW No provenance attestation provenance

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

v0.1.17

1 finding
LOW No provenance attestation provenance

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

v0.1.16

2 findings
HIGH env-spread: lib/commands/server.js:38 semgrep

Spreading entire process.env into an object — may capture all secrets 36 | async function startServer(opts) { 37 | const entry = require.resolve("@yinuo-ngm/server"); > 38 | const env = { 39 | ...process.env, 40 | ...(opts.port && { NGM_SERVER_PORT: String(opts.port) }),

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

1 finding
LOW No provenance attestation provenance

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

v0.1.9

1 finding
LOW No provenance attestation provenance

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

v0.1.8

1 finding
LOW No provenance attestation provenance

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

v0.1.7

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

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

2 findings
HIGH env-spread: lib/commands/server.js:14 semgrep

Spreading entire process.env into an object — may capture all secrets 12 | const serverDir = path_1.default.dirname(serverPkgJson); 13 | const entry = path_1.default.join(serverDir, "lib", "index.js"); > 14 | const env = { 15 | ...process.env, 16 | ...(opts.port && { NGM_SERVER_PORT: String(opts.port) }),

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.