@zhennann/common-bin
1
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
zhennann
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is the documented plugin/command-loading mechanism of common-bin. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process is core to common-bin's CLI subprocess execution feature. | ai | |
| semgrep | semgrep:child-process-spawn | AI (semgrep): spawn() is the intended mechanism for running subprocesses in this CLI framework. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped fork of a legitimate package; mass-production publisher pattern reflects monorepo maintenance, not spam. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 4.0.1 | 8 / 8 |
v4.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.