@async-fn/jest
Additional methods to jest.fn to introduce "late resolve" of promises returned by mock functions. This allows tests that read chronologically, like a story.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file-transition:build/index.js | AI (source-diff): Webpack-bundled lodash chunks, not obfuscation; build size grew due to new bundled dependency. | ai | |
| dependencies | unvetted-dep:@async-fn/core | AI (dependencies): Same-org sibling package (@async-fn scope), core dependency for this test helper. | ai | |
| typosquat | typosquat.levenshtein:next | AI (typosquat): Scoped Jest testing utility; name similarity to 'next' is coincidental, not impersonation. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.7.0 | 0 / 1 | |
| 1.6.5 | 0 / 1 | |
| 1.6.3 | 1 / 0 | |
| 1.2.2 | 0 / 5 | |
| 1.2.1 | 0 / 4 | |
| 1.2.0 | 0 / 4 | |
| 1.1.0 | 0 / 4 | |
| 1.0.0 | 0 / 4 |
v1.6.3
2 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jansav) than the most recent previously approved version (iku-turso) on 2020-08-12, but jansav is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (iku-turso) than the most recent previously approved version (jansav) on 2020-07-01, but iku-turso is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.