← Home

@yarnpkg/plugin-nm

npm Repository
8
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.

SourceRuleReasonAccepted byWhen
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

Versions (showing 8 of 8)

Version Deps Published
4.1.0 9 / 2
4.0.9 9 / 2
4.0.8 9 / 2
4.0.7 9 / 2
4.0.6 9 / 2
4.0.5 9 / 2
4.0.4 9 / 2
4.0.3 9 / 2

v4.0.6

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.5

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.4

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.