← Home

items

npm Repository Homepage

Bare minimum async methods

10
Versions
SEE LICENSE IN LICENSE.md
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

nargonathdevinivymarsupnlf

Keywords

asyncserialparallel

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Known hapijs ecosystem transition from hueniverse (Eran Hammer) to nargonath/devinivy; well-documented legitimate maintainer handoff, not a compromise. ai
maintainer-change maintainer-added AI (maintainer-change): nargonath and devinivy are recognized hapijs ecosystem maintainers who took over the project legitimately. ai
maintainer-change maintainer-removed AI (maintainer-change): hueniverse and wyatt stepped back from hapijs maintenance; this is a known, legitimate transition in the hapijs ecosystem. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy aligns with the period after hueniverse stepped away from hapijs; resumed activity by new legitimate maintainers is expected. ai

Versions (showing 10 of 10)

Version Deps Published
2.2.1 0 / 2
2.1.2 0 / 2
2.1.1 0 / 2
2.1.0 0 / 2
2.0.1 0 / 2
2.0.0 0 / 2
1.1.1 0 / 2
1.1.0 0 / 1
1.0.2 0 / 1
1.0.1 0 / 1

v2.2.1

2 findings
HIGH Publisher changed: hueniverse → nargonath (on 2024-01-06) provenance

This version was published by a different npm account than previous versions on 2024-01-06. 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.

v2.1.2

1 finding
LOW No provenance attestation provenance

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

v2.1.1

1 finding
LOW No provenance attestation provenance

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

v2.1.0

1 finding
LOW No provenance attestation provenance

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

v2.0.1

1 finding
LOW No provenance attestation provenance

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

v2.0.0

1 finding
LOW No provenance attestation provenance

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

v1.1.1

1 finding
LOW No provenance attestation provenance

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

v1.1.0

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: hueniverse → rockbot (on 2014-10-16) provenance

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

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.1

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.