← Home

async-array-reduce

Async array reduce. Asynchronously applies a function against an accumulator and each element in an array (from left to right, in series) to reduce it to a single value.

4
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

doowbjonschlinkert

Keywords

arrayasyncreduce

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Both doowb and jonschlinkert are listed contributors; jonschlinkert owns the GitHub repo. This is a documented legitimate transition, not a takeover. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy on a small utility package is expected; no material changes in the diff and the publisher is a well-known, trusted maintainer. ai

Versions (showing 4 of 4)

Version Deps Published
1.0.0 0 / 2
0.2.1 0 / 2
0.2.0 0 / 2
0.1.0 0 / 2

v1.0.0

2 findings
HIGH Publisher changed: doowb → jonschlinkert (on 2017-09-09) provenance

This version was published by a different npm account than previous versions on 2017-09-09. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.1

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: jonschlinkert → doowb (on 2016-11-17) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2016-11-17. This could indicate a legitimate maintainer transition or an account compromise.

v0.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.