@yuuvis/client-cli
CLI tool for yuuvis Momentum clients
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): CLI tool; child_process use is expected for running system commands in CLI command handlers. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): 127.0.0.1 in a proxy.config.js template file — localhost dev proxy, not exfiltration. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Loads local package.json via path.join; not user-controlled arbitrary module loading. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Documented npm _auth credential re-encoding; comment explains the pattern explicitly. | ai | |
| phantom-deps | phantom-dep:@angular-devkit/schematics-cli | AI (phantom-deps): Listed as a runtime dep and used via schematics config, not direct import; stable false positive. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 21.0.0 | 13 / 0 | |
| 19.10.0 | 13 / 0 | |
| 19.9.0 | 12 / 0 | |
| 19.8.0 | 11 / 0 | |
| 19.7.0 | 11 / 0 | |
| 19.6.0 | 11 / 0 | |
| 19.5.0 | 11 / 0 | |
| 19.4.0 | 10 / 0 | |
| 19.3.3 | 10 / 0 |
v21.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.