← Home

@munesoft/asyncx

npm Repository Homepage

Unified async control for JavaScript: retries, timeouts, caching, concurrency, cancellation, and circuit breakers — one function.

3
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

erickjongo

Keywords

asyncretrytimeoutcacheconcurrencyabortcircuit-breakerdeduplicationpromisetypescriptasync-retrypromise-timeoutrate-limitasync-cachejavascript-asyncnode-retryasync-controlpromise-queue

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:async AI (typosquat): Scoped package @munesoft/asyncx is not impersonating 'async'; distinct purpose and namespace make this a stable false positive. ai

Versions (showing 3 of 3)

Version Deps Published
1.204.12 0 / 4
1.101.11 0 / 4
1.101.10 0 / 4

v1.204.12

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'async' typosquat

Package name '@munesoft/asyncx' is 1 edit(s) away from popular package 'async'.

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.

v1.101.11

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'async' typosquat

Package name '@munesoft/asyncx' is 1 edit(s) away from popular package 'async'.

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.

v1.101.10

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'async' typosquat

Package name '@munesoft/asyncx' is 1 edit(s) away from popular package 'async'.

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.