@equisoft/jest-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 |
|---|---|---|---|---|
| typosquat | typosquat.pattern:jest | AI (typosquat): Scoped @equisoft org package; 'jest-utils' is a legitimate utility name, not a typosquat of jest. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.8.4 | 1 / 17 | |
| 1.8.3 | 1 / 17 | |
| 1.8.2 | 1 / 17 | |
| 1.8.1 | 1 / 17 | |
| 1.8.0 | 1 / 17 | |
| 1.7.2 | 1 / 16 | |
| 1.7.1 | 1 / 16 | |
| 1.7.0 | 1 / 16 |
v1.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.