pnpm-sync-lib
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@pnpm/dependency-path-pnpm-v8 | AI (dependencies): Aliased pin to official @pnpm/dependency-path package, standard multi-version support pattern. | ai | |
| dependencies | unvetted-dep:@pnpm/dependency-path-pnpm-v9 | AI (dependencies): Aliased pin to official @pnpm/dependency-path package, standard multi-version support pattern. | ai | |
| dependencies | unvetted-dep:@pnpm/dependency-path-pnpm-v10 | AI (dependencies): Aliased pin to official @pnpm/dependency-path package, standard multi-version support pattern. | ai | |
| dependencies | unvetted-dep:@pnpm/lockfile-types-pnpm-lock-v6 | AI (dependencies): Aliased pin to official @pnpm/lockfile-types package for lockfile v6 support. | ai | |
| dependencies | unvetted-dep:@pnpm/lockfile.types-pnpm-lock-v9 | AI (dependencies): Aliased pin to official @pnpm/lockfile.types package for lockfile v9 support. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.3.4 | 6 / 8 | |
| 0.3.3 | 6 / 8 | |
| 0.3.0 | 2 / 8 | |
| 0.2.9 | 2 / 8 | |
| 0.2.8 | 2 / 8 |
v0.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.