@yarnpkg/plugin-nm
3
Versions
—
License
No
Install Scripts
Verified
Provenance
Supply chain provenance
Status for the latest visible version.
SLSA provenance attestation
npm registry signatures
gitHead linked
Maintainers
arcanisyarnbot
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): yarnbot is the official Yarn Berry CI publisher; transition from arcanis is expected and backed by SLSA provenance. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Yarn Berry consolidates publishing under yarnbot automation; maintainer list changes are expected org-wide. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): 103 versions in registry; batch/coordinated release cadence explains apparent dormancy gaps. | ai | |
| dependencies | unvetted-dep:@yarnpkg/plugin-pnp | AI (dependencies): First-party @yarnpkg/* dependency within the same Yarn Berry monorepo; not a third-party risk. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Official Yarn Berry plugin; missing description is a known pattern across the monorepo, not a risk indicator. | ai | |
| provenance | no-provenance | AI (provenance): Established Yarn Berry package; lack of provenance is consistent across the monorepo and not a risk signal here. | ai |
v4.0.9
2 findings
HIGH
Publisher changed: arcanis → yarnbot (on 2026-05-19)
provenance
This version was published by a different npm account than previous versions on 2026-05-19. This could indicate a legitimate maintainer transition or an account compromise.
INFO
Has SLSA provenance attestation
provenance
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.8
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.7
1 finding
INFO
Has SLSA provenance attestation
provenance
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.