simple-bin-help
Simple help and sanity checks for Node CLI bin scripts
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:dynamic-require | AI (semgrep): dynamic require() is intentional here — the package accepts a packagePath option so callers can supply their own package.json path. This is the documented API, not a security risk. | ai | |
| provenance | no-provenance | AI (provenance): Established package from a trusted publisher; lack of Sigstore provenance is common and not a risk signal for this package. | ai | |
| source-diff | obfuscated-file:dist/index.js | AI (source-diff): dist/index.js is an esbuild bundle of src/index.js as declared in the build script. The 'obfuscation' is standard esbuild runtime boilerplate, not malicious code. Stable for this package. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase is due to bundling former runtime deps (debug, update-notifier, word-wrap) into the esbuild dist output. Legitimate refactor, stable for this package. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 1.8.0 | 0 / 9 | |
| 1.7.8 | 3 / 6 | |
| 1.7.7 | 3 / 6 | |
| 1.7.6 | 3 / 6 | |
| 1.7.5 | 3 / 6 | |
| 1.7.1 | 3 / 8 | |
| 1.7.0 | 3 / 7 | |
| 1.6.0 | 2 / 7 | |
| 1.5.1 | 2 / 7 | |
| 1.5.0 | 2 / 7 | |
| 1.4.0 | 2 / 7 | |
| 1.3.0 | 1 / 7 | |
| 1.2.0 | 0 / 6 | |
| 1.1.0 | 0 / 6 | |
| 1.0.0 | 0 / 6 |
v1.8.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.