jest-jasmine2
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): jest-jasmine2 is a well-known Jest subpackage; missing description is cosmetic, not suspicious. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): @types/node is a type-only dep declared for TS consumers; standard pattern. | ai |
Versions (showing 51 of 187)
| Version | Deps | Published |
|---|---|---|
| 30.3.0 | 17 / 1 | |
| 30.2.0 | 17 / 1 | |
| 30.1.3 | 17 / 1 | |
| 30.1.2 | 17 / 1 | |
| 30.1.1 | 17 / 1 | |
| 30.1.0 | 17 / 1 | |
| 30.0.5 | 17 / 1 | |
| 30.0.4 | 17 / 1 | |
| 30.0.3 | 17 / 1 | |
| 30.0.2 | 17 / 1 | |
| 30.0.1 | 17 / 1 | |
| 30.0.0 | 17 / 1 | |
| 29.7.0 | 17 / 1 | |
| 29.6.4 | 17 / 1 | |
| 29.6.3 | 17 / 1 | |
| 29.6.2 | 17 / 1 | |
| 29.6.1 | 17 / 1 | |
| 29.6.0 | 17 / 1 | |
| 29.5.0 | 17 / 1 | |
| 29.4.3 | 17 / 1 | |
| 29.4.2 | 17 / 1 | |
| 29.4.1 | 17 / 1 | |
| 29.4.0 | 17 / 1 | |
| 29.3.1 | 17 / 1 | |
| 29.3.0 | 17 / 1 | |
| 29.2.2 | 17 / 1 | |
| 29.2.1 | 17 / 1 | |
| 29.2.0 | 17 / 1 | |
| 29.1.2 | 17 / 1 | |
| 29.1.1 | 17 / 1 | |
| 29.1.0 | 17 / 1 | |
| 29.0.3 | 17 / 1 | |
| 29.0.2 | 17 / 1 | |
| 29.0.1 | 17 / 1 | |
| 29.0.0 | 17 / 1 | |
| 28.1.3 | 17 / 1 | |
| 28.1.2 | 17 / 1 | |
| 28.1.1 | 17 / 1 | |
| 28.1.0 | 17 / 1 | |
| 28.0.3 | 17 / 1 | |
| 28.0.2 | 17 / 1 | |
| 28.0.1 | 17 / 1 | |
| 28.0.0 | 17 / 1 | |
| 27.5.1 | 17 / 1 | |
| 27.5.0 | 17 / 1 | |
| 27.4.6 | 17 / 1 | |
| 27.4.5 | 18 / 2 | |
| 27.4.4 | 18 / 2 | |
| 27.4.2 | 18 / 2 | |
| 27.4.1 | 18 / 2 | |
| 27.4.0 | 18 / 2 |
v30.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.0.0
2 findingsThis version was published by a different npm account than previous versions on 2025-06-10. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.