jest-snapshot MIT 59 versions

jest-snapshot

npm Repository

59

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.

Source	Rule	Reason	Accepted by	When
npm-metadata	suspicious-initial-version	AI (npm-metadata): jest-snapshot 0.0.0 is a namespace reservation by the official Jest maintainer (cpojer); the 0.0.0 version is a known placeholder pattern for this established package.	ai	2026/04/23
npm-metadata	no-description	AI (npm-metadata): Placeholder/stub release by trusted publisher; missing description is expected for a namespace reservation, not a malicious signal.	ai	2026/04/23
provenance	publisher-changed	AI (provenance): simenb (Simen Bekkhus) is a well-known Jest core maintainer; the cpojer→simenb transition is a documented, legitimate handoff within the Jest team, not a compromise.	ai	2026/04/23
publish-pattern	new-deps-added	AI (publish-pattern): Diff is against v19.0.2; 18 new deps reflect 10 major versions of legitimate Jest development. All added packages are standard, well-known ecosystem packages.	ai	2026/04/23
phantom-deps	phantom-dep:@types/babel__traverse	AI (phantom-deps): @types/babel__traverse is a TypeScript type package; phantom-dep finding is a stable false positive for this package.	ai	2026/04/23
phantom-deps	phantom-dep:@types/prettier	AI (phantom-deps): @types/prettier is a TypeScript type package used for type inference; not directly imported at runtime by convention. Stable false positive for this package.	ai	2026/04/23
maintainer-change	maintainer-removed	AI (maintainer-change): Removed maintainers are former Facebook employees; removal is consistent with the well-documented Jest governance transfer from Meta to the OpenJS Foundation.	ai	2026/04/23
maintainer-change	maintainer-added	AI (maintainer-change): New maintainers reflect the documented Jest transition to the OpenJS Foundation; aaronabramov, simenb, rickhanlonii are known Jest contributors and openjs-operations is the OpenJS Foundation npm account.	ai	2026/04/23
source-diff	source-size-tripled	AI (source-diff): Size increase from v19 to v30 reflects a major version with significant new Babel integration and snapshot utility features; not indicative of injected payload.	ai	2026/04/23
bogus-package	bogus-package	AI (bogus-package): jest-snapshot is an official Jest monorepo package; inflated semver, no description, and no keywords are expected characteristics of this package, not spam indicators.	ai	2026/04/21
phantom-deps	phantom-dep:@babel/types	AI (phantom-deps): @babel/types is a legitimate declared dependency used for Babel AST type definitions; phantom detection is a false positive for this Babel-integrated package.	ai	2026/04/21

Versions (showing 59 of 159)

Version	Deps	Published
24.5.0	12 / 6	2019-03-12
24.4.0	12 / 6	2019-03-11
24.3.1	12 / 6	2019-03-07
24.3.0	12 / 6	2019-03-07
24.1.0	10 / 1	2019-02-05
24.0.0	10 / 1	2019-01-25
23.6.0	10 / 1	2018-09-10
23.5.0	10 / 1	2018-08-10
23.4.2	10 / 1	2018-07-27
23.4.1	11 / 1	2018-07-13
23.4.0	11 / 1	2018-07-10
23.3.0	11 / 1	2018-07-04
23.2.0	6 / 0	2018-06-25
23.0.1	6 / 0	2018-05-27
23.0.0	6 / 0	2018-05-24
22.4.3	6 / 0	2018-03-21
22.4.0	6 / 0	2018-02-20
22.2.0	6 / 0	2018-02-07
22.1.2	6 / 0	2018-01-17
22.1.0	6 / 0	2018-01-15
22.0.6	6 / 0	2018-01-11
22.0.5	6 / 0	2018-01-09
22.0.3	6 / 0	2017-12-19
22.0.2	6 / 0	2017-12-19
22.0.1	6 / 0	2017-12-18
22.0.0	6 / 0	2017-12-18
21.2.1	6 / 0	2017-09-27
21.2.0	6 / 0	2017-09-26
21.1.0	6 / 0	2017-09-14
21.0.2	6 / 0	2017-09-08
21.0.0	6 / 0	2017-09-04
20.0.3	6 / 0	2017-05-17
20.0.2	6 / 0	2017-05-17
20.0.1	6 / 0	2017-05-11
20.0.0	6 / 0	2017-05-06
19.0.2	7 / 0	2017-02-23
19.0.1	7 / 0	2017-02-22
19.0.0	7 / 0	2017-02-21
18.1.0	6 / 0	2016-12-29
18.0.0	6 / 0	2016-12-15
17.0.3	6 / 0	2016-11-17
17.0.2	6 / 0	2016-11-15
17.0.1	6 / 0	2016-11-14
17.0.0	6 / 0	2016-11-08
16.0.2	6 / 0	2016-10-20
16.0.0	6 / 0	2016-10-03
15.1.1	4 / 0	2016-09-02
15.1.0	4 / 0	2016-09-01
15.0.1	4 / 0	2016-09-01
15.0.0	4 / 0	2016-08-31
14.0.0	4 / 0	2016-07-27
13.2.3	2 / 0	2016-07-07
13.2.2	2 / 0	2016-07-07
13.2.1	2 / 0	2016-07-07
13.1.2	2 / 0	2016-07-07
13.1.1	2 / 0	2016-07-06
13.1.0	2 / 0	2016-07-05
13.0.0	2 / 0	2016-06-22
0.0.0	0 / 0	2016-04-28

v24.5.0

1 finding

LOW No provenance attestation provenance

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

v24.4.0

1 finding

LOW No provenance attestation provenance

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

v24.3.1

1 finding

LOW No provenance attestation provenance

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

v24.3.0

1 finding

LOW No provenance attestation provenance

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

v24.1.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: mjesun → rubennorte (on 2019-02-05) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-02-05. This could indicate a legitimate maintainer transition or an account compromise.

v24.0.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: mjesun → rubennorte (on 2019-01-25) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-01-25. This could indicate a legitimate maintainer transition or an account compromise.

v23.6.0

1 finding

LOW No provenance attestation provenance

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

v23.5.0

1 finding

LOW No provenance attestation provenance

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

v23.4.2

1 finding

LOW No provenance attestation provenance

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

v23.4.1

1 finding

LOW No provenance attestation provenance

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

v23.4.0

1 finding

LOW No provenance attestation provenance

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

v23.3.0

1 finding

LOW No provenance attestation provenance

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

v23.2.0

1 finding

LOW No provenance attestation provenance

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

v23.0.1

1 finding

LOW No provenance attestation provenance

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

v23.0.0

1 finding

LOW No provenance attestation provenance

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

v22.4.3

1 finding

LOW No provenance attestation provenance

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

v22.4.0

1 finding

LOW No provenance attestation provenance

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

v22.2.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: cpojer → mjesun (on 2018-02-07) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-02-07. This could indicate a legitimate maintainer transition or an account compromise.

v22.1.2

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: cpojer → mjesun (on 2018-01-17) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-01-17. This could indicate a legitimate maintainer transition or an account compromise.

v22.1.0

1 finding

LOW No provenance attestation provenance

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

v22.0.6

1 finding

LOW No provenance attestation provenance

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

v22.0.5

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: cpojer → mjesun (on 2018-01-09) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-01-09. This could indicate a legitimate maintainer transition or an account compromise.

v22.0.3

1 finding

LOW No provenance attestation provenance

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

v22.0.2

1 finding

LOW No provenance attestation provenance

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

v22.0.1

1 finding

LOW No provenance attestation provenance

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

v22.0.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: cpojer → mjesun (on 2017-12-18) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2017-12-18. This could indicate a legitimate maintainer transition or an account compromise.

v21.2.1

1 finding

LOW No provenance attestation provenance

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

v21.2.0

1 finding

LOW No provenance attestation provenance

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

v21.1.0

1 finding

LOW No provenance attestation provenance

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

v21.0.2

1 finding

LOW No provenance attestation provenance

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

v21.0.0

1 finding

LOW No provenance attestation provenance

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

v20.0.3

1 finding

LOW No provenance attestation provenance

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

v20.0.2

1 finding

LOW No provenance attestation provenance

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

v20.0.1

1 finding

LOW No provenance attestation provenance

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

v20.0.0

1 finding

LOW No provenance attestation provenance

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

v19.0.2

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.

v19.0.1

1 finding

LOW No provenance attestation provenance

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

v19.0.0

1 finding

LOW No provenance attestation provenance

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

v18.1.0

1 finding

LOW No provenance attestation provenance

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

v18.0.0

1 finding

LOW No provenance attestation provenance

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

v17.0.3

1 finding

LOW No provenance attestation provenance

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

v17.0.2

1 finding

LOW No provenance attestation provenance

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

v17.0.1

1 finding

LOW No provenance attestation provenance

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

v17.0.0

1 finding

LOW No provenance attestation provenance

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

v16.0.2

1 finding

LOW No provenance attestation provenance

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

v16.0.0

1 finding

LOW No provenance attestation provenance

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

v15.1.1

1 finding

LOW No provenance attestation provenance

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

v15.1.0

1 finding

LOW No provenance attestation provenance

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

v15.0.1

1 finding

LOW No provenance attestation provenance

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

v15.0.0

1 finding

LOW No provenance attestation provenance

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

v14.0.0

1 finding

LOW No provenance attestation provenance

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

v13.2.3

1 finding

LOW No provenance attestation provenance

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

v13.2.2

1 finding

LOW No provenance attestation provenance

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

v13.2.1

1 finding

LOW No provenance attestation provenance

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

v13.1.2

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.

v13.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.

v13.1.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.

v13.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.

v0.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.