@jest/snapshot-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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): simenb is a known Jest core maintainer; rotation from cpojer is legitimate. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo sub-package; missing description is cosmetic, not suspicious. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): eval() is in a test file verifying snapshot round-trip serialization — intentional test pattern, not production supply-chain risk. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function() is Jest's documented mechanism for loading .snap files (CommonJS modules); stable and intentional across all Jest versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Inflated semver and missing metadata are explained by this being a newly extracted monorepo sub-package versioned in lockstep with Jest 30.x. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 30.4.1 | 4 / 2 | |
| 30.4.0 | 4 / 2 | |
| 30.3.0 | 4 / 2 | |
| 30.2.0 | 4 / 2 | |
| 30.1.2 | 4 / 2 | |
| 30.1.1 | 4 / 2 | |
| 30.1.0 | 4 / 2 | |
| 30.0.5 | 4 / 2 | |
| 30.0.4 | 4 / 2 | |
| 30.0.1 | 4 / 2 | |
| 30.0.0 | 4 / 2 |
v30.4.1
2 findingsThis version was published by a different npm account than previous versions on 2026-05-08. 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.
v30.4.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-07. 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.
v30.2.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v30.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v30.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v30.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.