npm-to-yarn
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Same individual maintainer under new npm account; no behavior change in diff. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Corresponds to same author's account transition, not a takeover. | ai | |
| provenance | missing-githead | AI (provenance): Publish-env change only; no payload change, benign for this owner-maintained package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long-lived popular pkg; dormancy alone not malicious, no code-level signal. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 3.2.0 | 0 / 14 | |
| 3.1.0 | 0 / 14 | |
| 3.0.1 | 0 / 14 | |
| 3.0.0 | 0 / 14 |
v3.2.0
2 findingsThis version was published by a different npm account than previous versions on 2026-07-24. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nebrelbug.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.