@flemist/async-utils
Simple async utils
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): Known implicit dependency from TypeScript transpilation; stable across versions. | ai | |
| phantom-deps | phantom-dep:setimmediate | AI (phantom-deps): Referenced in build config; stable polyfill dependency for this package. | ai | |
| phantom-deps | phantom-dep:@flemist/time-controller | AI (phantom-deps): Same-org scoped package; internal dependency pattern for this publisher. | ai | |
| phantom-deps | phantom-dep:@flemist/abort-controller-fast | AI (phantom-deps): Same-org scoped package; internal dependency pattern for this publisher. | ai | |
| typosquat | typosquat.pattern:async | AI (typosquat): Scoped @flemist package by the same author; not impersonating the 'async' package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.2.10 | 4 / 48 | |
| 1.2.9 | 4 / 48 | |
| 1.2.8 | 4 / 47 | |
| 1.2.7 | 4 / 47 | |
| 1.2.5 | 4 / 47 | |
| 1.2.4 | 4 / 47 | |
| 1.2.3 | 4 / 47 | |
| 1.2.2 | 4 / 47 | |
| 1.2.1 | 4 / 47 | |
| 1.2.0 | 4 / 47 |
v1.2.10
2 findingsPackage name '@flemist/async-utils' matches a known typosquatting pattern (hyphen swap, prefix/suffix) of 'async'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.