option-chain
Use fluent property chains in lieu of options objects
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
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): Transfer from jamestalmage to sindresorhus is a legitimate handoff within the avajs org; both are well-known AVA ecosystem maintainers. Verdict generalizes to this package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): sindresorhus added as maintainer is consistent with the known avajs/jamestalmage collaboration; not a suspicious takeover. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by publish reflects a legitimate ownership transfer, not account takeover. Publisher identity (sindresorhus) is highly trusted. | ai |
v1.0.0
2 findingsThis version was published by a different npm account than previous versions on 2017-05-12. 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.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.