chunkify
Split an iterable into evenly sized chunks
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-takeover | AI (maintainer-change): Takeover is a legitimate transfer to sindresorhus, a canonical trusted npm publisher. Package structure and repo URL confirm authentic ownership. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change to sindresorhus is a legitimate adoption. sindresorhus is one of the most trusted npm publishers with thousands of approved packages. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): sindresorhus added as maintainer is a legitimate transfer, not a compromise. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Original maintainer removal is consistent with a full package transfer to sindresorhus. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long dormancy followed by sindresorhus publish is a known pattern of adopting/rewriting abandoned utility packages. | ai | |
| source-diff | source-size-dropped | AI (source-diff): Size drop from 16KB to 1KB reflects rewrite as minimal ESM-only module; removed compile/dev scripts confirm elimination of build pipeline. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 5.0.0 | 0 / 3 | |
| 4.0.0 | 0 / 14 | |
| 3.0.6 | 1 / 7 | |
| 3.0.5 | 4 / 7 | |
| 3.0.4 | 4 / 7 | |
| 3.0.3 | 4 / 7 | |
| 3.0.1 | 4 / 7 | |
| 3.0.0 | 4 / 7 | |
| 2.1.1 | 4 / 10 | |
| 2.1.0 | 4 / 10 | |
| 2.0.4 | 4 / 7 | |
| 2.0.3 | 4 / 7 | |
| 2.0.2 | 4 / 7 | |
| 2.0.1 | 4 / 7 | |
| 2.0.0 | 3 / 8 | |
| 1.0.5 | 3 / 8 | |
| 1.0.4 | 3 / 8 | |
| 1.0.3 | 3 / 8 | |
| 1.0.2 | 0 / 11 | |
| 1.0.1 | 0 / 11 | |
| 1.0.0 | 0 / 0 |
v5.0.0
3 findingsAll previous maintainers (yangmillstheory) were replaced by new maintainers (sindresorhus). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2023-12-27. 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.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.