@pnpm/link-bins
Link bins to node_modules/.bin
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@zkochan/cmd-shim | AI (dependencies): @zkochan/cmd-shim is a well-known Windows cmd shim utility authored by pnpm's lead maintainer; its use here is expected and legitimate. | ai | |
| dependencies | unvetted-dep:@pnpm/package-bins | AI (dependencies): Core pnpm monorepo package; its inclusion in @pnpm/link-bins is expected and consistent across all versions. | ai | |
| dependencies | unvetted-dep:@pnpm/manifest-utils | AI (dependencies): Core pnpm monorepo package; its inclusion in @pnpm/link-bins is expected and consistent across all versions. | ai | |
| dependencies | unvetted-dep:@pnpm/read-project-manifest | AI (dependencies): Core pnpm monorepo package; its inclusion in @pnpm/link-bins is expected and consistent across all versions. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 1000.3.9 | 17 / 11 | |
| 1000.3.8 | 17 / 11 | |
| 1000.3.7 | 17 / 11 | |
| 1000.3.6 | 17 / 11 | |
| 1000.3.5 | 17 / 11 | |
| 1000.3.4 | 17 / 11 | |
| 1000.3.3 | 17 / 11 | |
| 1000.3.2 | 17 / 11 | |
| 1000.3.1 | 17 / 11 | |
| 1000.3.0 | 17 / 11 | |
| 1000.2.6 | 17 / 11 | |
| 1000.2.5 | 17 / 11 | |
| 1000.2.4 | 17 / 11 | |
| 1000.2.3 | 17 / 11 | |
| 1000.2.2 | 17 / 11 | |
| 1000.2.1 | 17 / 11 | |
| 1000.2.0 | 18 / 10 | |
| 1000.1.0 | 18 / 10 | |
| 1000.0.13 | 17 / 10 | |
| 1000.0.12 | 17 / 10 | |
| 1000.0.11 | 17 / 10 | |
| 1000.0.10 | 17 / 10 | |
| 1000.0.9 | 17 / 10 | |
| 1000.0.8 | 17 / 10 | |
| 1000.0.7 | 17 / 10 | |
| 1000.0.6 | 17 / 10 | |
| 1000.0.5 | 17 / 10 | |
| 1000.0.4 | 17 / 10 | |
| 1000.0.3 | 17 / 10 | |
| 1000.0.2 | 17 / 10 | |
| 1000.0.1 | 17 / 10 | |
| 1000.0.0 | 17 / 10 |
v1000.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.