← Home

asyncjs

npm Repository Homepage

async.js it for the node fs module, what jQuery is for the DOM

12
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

fjakobs

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:async AI (typosquat): asyncjs is a distinct, legitimate async utility library by Fabian Jakobs with its own GitHub repo and 5500+ day history — not a typosquat of async. ai
bogus-package bogus-package AI (bogus-package): Low metadata score is due to age-related conventions (no description/keywords); package has a real author, repo, and download history. ai
semgrep semgrep:new-function-constructor AI (semgrep): Usage is `new Function()` as a no-op default callback — not dynamic code execution from external input. Benign pattern stable across versions of this package. ai
semgrep semgrep:child-process-import AI (semgrep): spawn is imported in a filesystem plugin (fs-node.js) consistent with this library's documented purpose of wrapping Node.js fs operations. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require is in lib/test.js (test infrastructure), loading test cases by path. Not in runtime library code; stable false positive for this package. ai

Versions (showing 12 of 12)

Version Deps Published
0.0.13 0 / 0
0.0.12 0 / 0
0.0.11 0 / 0
0.0.10 0 / 0
0.0.9 0 / 0
0.0.8 0 / 0
0.0.7 0 / 0
0.0.6 0 / 0
0.0.5 0 / 0
0.0.4 0 / 0
0.0.2 0 / 0
0.0.1 0 / 0

v0.0.13

1 finding
LOW No provenance attestation provenance

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

v0.0.12

1 finding
LOW No provenance attestation provenance

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

v0.0.11

1 finding
LOW No provenance attestation provenance

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

v0.0.10

1 finding
LOW No provenance attestation provenance

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

v0.0.9

1 finding
LOW No provenance attestation provenance

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

v0.0.8

1 finding
LOW No provenance attestation provenance

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

v0.0.7

1 finding
LOW No provenance attestation provenance

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

v0.0.6

1 finding
LOW No provenance attestation provenance

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

v0.0.5

1 finding
LOW No provenance attestation provenance

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

v0.0.4

1 finding
LOW No provenance attestation provenance

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

v0.0.2

1 finding
LOW No provenance attestation provenance

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

v0.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.