@akanjs/test
This package is a sub-library of akanjs. For more information, please refer to [@akanjs/cli](https://www.npmjs.com/package/@akanjs/cli) and the [Akan.js Github](https://github.com/akan-team/akanjs).
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:next | AI (typosquat): Scoped package; no impersonation of next. | ai | |
| typosquat | typosquat.levenshtein:vitest | AI (typosquat): Scoped package; no impersonation of vitest. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): Scoped package @akanjs/test is a test utility, not a typosquat of jest. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in jest globalSetup loads user project files by design. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Raw IP is localhost default (127.0.0.1:4200) in Playwright config — standard dev pattern. | ai | |
| phantom-deps | phantom-dep:ts-jest | AI (phantom-deps): ts-jest is a declared dependency used in jest config exports, not a phantom dep. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 1.0.21 | 9 / 0 | |
| 1.0.20 | 9 / 0 | |
| 1.0.19 | 9 / 0 | |
| 1.0.18 | 9 / 0 | |
| 1.0.17 | 9 / 0 | |
| 1.0.16 | 9 / 0 | |
| 1.0.15 | 9 / 0 | |
| 1.0.14 | 9 / 0 | |
| 1.0.13 | 9 / 0 | |
| 1.0.12 | 9 / 0 | |
| 1.0.11 | 9 / 0 | |
| 1.0.10 | 9 / 0 | |
| 1.0.9 | 9 / 0 | |
| 1.0.8 | 9 / 0 | |
| 1.0.7 | 9 / 0 | |
| 1.0.6 | 9 / 0 | |
| 1.0.5 | 9 / 0 | |
| 1.0.4 | 9 / 0 | |
| 1.0.3 | 9 / 0 | |
| 1.0.2 | 9 / 0 | |
| 1.0.1 | 9 / 0 | |
| 1.0.0 | 9 / 0 | |
| 0.9.59 | 9 / 0 | |
| 0.9.58 | 9 / 0 | |
| 0.9.57 | 9 / 0 | |
| 0.9.56 | 9 / 0 | |
| 0.9.55 | 9 / 0 |
v1.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.14
2 findingsPackage name '@akanjs/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.