@yarnpkg/plugin-pnp
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established publisher with 153 approved versions; lack of provenance is consistent across all prior releases. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Official @yarnpkg scoped plugin; missing description is a known pattern for this monorepo, not a malware indicator. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 4.1.6 | 6 / 3 | |
| 4.1.5 | 6 / 3 | |
| 4.1.4 | 6 / 3 | |
| 4.1.3 | 6 / 3 | |
| 4.1.2 | 6 / 3 | |
| 4.1.1 | 6 / 3 |
v4.1.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.