← Home

@jest/snapshot-utils

npm Repository
9
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

aaronabramovsimenbrickhanloniiopenjs-operationscpojer

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 9 of 9)

Version Deps Published
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.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v30.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v30.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v30.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v30.0.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v30.0.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v30.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v30.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.