list-item
Generate a single formatted list item, allowing you to easily generate lists with proper indentation, bullets, numbers or other leading characters.
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): adjohnson916 is a listed co-maintainer with a strong npm track record (114 approved, 0 rejected). Transfer occurred in 2015 and is clearly legitimate. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): adjohnson916 added as co-maintainer alongside jonschlinkert; long-standing collaborator with clean record. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.0.0 | 2 / 3 | |
| 1.1.1 | 4 / 3 | |
| 1.1.0 | 4 / 3 | |
| 1.0.1 | 3 / 4 | |
| 0.1.2 | 3 / 3 | |
| 0.1.1 | 3 / 3 | |
| 0.1.0 | 3 / 3 |
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
2 findingsThis version was published by a different npm account than previous versions on 2015-08-08. 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.