group-array
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): jonschlinkert was already a listed contributor; transition from doowb is legitimate. jonschlinkert has a strong 4611-day track record with 2859 approved packages. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): arr-flatten, for-own, and union-value are well-known ecosystem utilities already referenced in the package's verb.related config; no suspicious deps introduced. | ai | |
| provenance | no-provenance | AI (provenance): Package predates npm provenance attestations by years; absence is expected and not a risk signal for this established package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.0.0 | 6 / 3 | |
| 0.3.4 | 6 / 3 | |
| 0.3.3 | 6 / 3 | |
| 0.3.2 | 5 / 3 | |
| 0.3.1 | 2 / 5 | |
| 0.3.0 | 2 / 5 | |
| 0.2.0 | 2 / 5 | |
| 0.1.1 | 3 / 1 | |
| 0.1.0 | 3 / 1 |
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
2 findingsThis version was published by a different npm account than previous versions on 2017-02-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.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.