@yarn-tool/check-pkg-bin
check pkg bin has shebang
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:ws-pkg-list | AI (dependencies): Same-author package from bluelovers ecosystem; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:debug-color2 | AI (dependencies): Same-author package from bluelovers ecosystem; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@yarn-tool/table | AI (dependencies): First-party @yarn-tool package from same monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@yarn-tool/find-root | AI (dependencies): First-party @yarn-tool package from same monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@bluelovers/string-natural-compare | AI (dependencies): Same-author @bluelovers package; stable false positive for this package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 4.0.10 | 14 / 0 | |
| 4.0.9 | 14 / 0 | |
| 4.0.8 | 14 / 0 | |
| 4.0.7 | 14 / 0 | |
| 4.0.4 | 14 / 0 | |
| 4.0.3 | 14 / 0 | |
| 4.0.2 | 14 / 0 | |
| 4.0.1 | 14 / 0 |
v4.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.