@jest/fake-timers MIT 90 versions

@jest/fake-timers

npm Repository

90

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
maintainer-change	maintainer-removed	AI (maintainer-change): Removal of jeanlauliac is consistent with documented Jest team evolution; no takeover indicators.	ai	2026/04/22
provenance	publisher-changed	AI (provenance): simenb is a well-known Jest core maintainer; publisher change reflects legitimate Jest team transition, not a compromise.	ai	2026/04/22
maintainer-change	maintainer-added	AI (maintainer-change): simenb and davidzilburg are documented Jest core contributors; additions reflect legitimate team changes.	ai	2026/04/22
publish-pattern	new-deps-added	AI (publish-pattern): New deps (@sinonjs/fake-timers, @types/node, jest-util) are well-established packages added as part of Jest 26's documented architectural changes.	ai	2026/04/22
npm-metadata	no-description	AI (npm-metadata): Monorepo package with documentation in main Jest repo; missing description is expected.	ai	2026/04/22
phantom-deps	phantom-dep:@jest/types	AI (phantom-deps): Framework-scoped Jest package loaded by convention; stable pattern for Jest monorepo packages.	ai	2026/04/22
phantom-deps	phantom-dep:@types/node	AI (phantom-deps): Type definitions loaded by convention; stable pattern for Jest monorepo packages.	ai	2026/04/22
bogus-package	bogus-package	AI (bogus-package): Jest monorepo sub-package; inflated semver tracks parent project version (Jest v30.x), no description is normal for monorepo packages. Not a spam/malicious indicator.	ai	2026/04/21
dependencies	unvetted-dep:@sinonjs/fake-timers	AI (dependencies): @sinonjs/fake-timers is the canonical fake timers library; a well-known, legitimate dependency that Jest has used for years.	ai	2026/04/21

Versions (showing 90 of 90)

Version	Deps	Published
30.4.1	6 / 1	2026-05-08
30.4.0	6 / 1	2026-05-07
30.3.0	6 / 2	2026-03-10
30.2.0	6 / 2	2025-09-28
30.1.2	6 / 2	2025-09-01
30.1.1	6 / 2	2025-08-27
30.1.0	6 / 2	2025-08-27
30.0.5	6 / 2	2025-07-22
30.0.4	6 / 2	2025-07-02
30.0.2	6 / 2	2025-06-19
30.0.1	6 / 2	2025-06-18
30.0.0	6 / 2	2025-06-10
29.7.0	6 / 2	2023-09-12
29.6.4	6 / 2	2023-08-24
29.6.3	6 / 2	2023-08-21
29.6.2	6 / 2	2023-07-27
29.6.1	6 / 2	2023-07-06
29.6.0	6 / 2	2023-07-04
29.5.0	6 / 2	2023-03-06
29.4.3	6 / 2	2023-02-15
29.4.2	6 / 2	2023-02-07
29.4.1	6 / 2	2023-01-26
29.4.0	6 / 2	2023-01-24
29.3.1	6 / 2	2022-11-08
29.3.0	6 / 2	2022-11-07
29.2.2	6 / 2	2022-10-24
29.2.1	6 / 2	2022-10-18
29.2.0	6 / 2	2022-10-14
29.1.2	6 / 2	2022-09-30
29.1.1	6 / 2	2022-09-28
29.1.0	6 / 2	2022-09-28
29.0.3	6 / 2	2022-09-10
29.0.2	6 / 2	2022-09-03
29.0.1	6 / 2	2022-08-26
29.0.0	6 / 2	2022-08-25
28.1.3	6 / 2	2022-07-13
28.1.2	6 / 2	2022-06-29
28.1.1	6 / 2	2022-06-07
28.1.0	6 / 2	2022-05-06
28.0.2	6 / 2	2022-04-27
28.0.1	6 / 2	2022-04-26
28.0.0	6 / 2	2022-04-25
27.5.1	6 / 1	2022-02-08
27.5.0	6 / 2	2022-02-05
27.4.6	6 / 2	2022-01-04
27.4.2	6 / 2	2021-11-30
27.4.1	6 / 2	2021-11-30
27.4.0	6 / 2	2021-11-29
27.3.1	6 / 2	2021-10-19
27.3.0	6 / 2	2021-10-17
27.2.5	6 / 2	2021-10-08
27.2.4	6 / 2	2021-09-29
27.2.3	6 / 2	2021-09-28
27.2.2	6 / 2	2021-09-25
27.2.0	6 / 2	2021-09-13
27.1.1	6 / 2	2021-09-08
27.1.0	6 / 2	2021-08-27
27.0.6	6 / 2	2021-06-28
27.0.5	6 / 2	2021-06-22
27.0.3	6 / 2	2021-05-29
27.0.2	6 / 2	2021-05-29
27.0.1	6 / 2	2021-05-25
27.0.0	6 / 2	2021-05-25
26.6.2	6 / 2	2020-11-02
26.6.1	6 / 1	2020-10-23
26.6.0	6 / 1	2020-10-19
26.5.2	6 / 1	2020-10-06
26.5.0	6 / 1	2020-10-05
26.3.0	6 / 1	2020-08-10
26.2.0	6 / 1	2020-07-30
26.1.0	5 / 2	2020-06-23
26.0.1	5 / 2	2020-05-05
26.0.0	5 / 2	2020-05-04
25.5.0	5 / 2	2020-04-28
25.4.0	5 / 2	2020-04-19
25.3.0	5 / 2	2020-04-08
25.2.6	5 / 2	2020-04-02
25.2.4	5 / 2	2020-03-29
25.2.3	5 / 2	2020-03-26
25.2.1	5 / 2	2020-03-26
25.2.0	5 / 2	2020-03-25
25.1.0	5 / 1	2020-01-22
25.0.0	3 / 0	2019-08-22
24.9.0	3 / 0	2019-08-16
24.8.0	3 / 0	2019-05-05
24.7.1	3 / 0	2019-04-04
24.7.0	3 / 0	2019-04-03
24.6.0	3 / 0	2019-04-01
24.5.0	4 / 0	2019-03-12
24.3.0	4 / 0	2019-03-07

v30.4.1

1 finding

LOW No provenance attestation provenance

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

v30.4.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 → simenb (on 2026-05-07) provenance

[Accepted risk] This 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.

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. Consider requesting the maintainer enable provenance via CI/CD.

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. Consider requesting the maintainer enable provenance via CI/CD.

v30.0.4

1 finding

LOW No provenance attestation provenance

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

v30.0.2

1 finding

LOW No provenance attestation provenance

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

v30.0.1

1 finding

LOW No provenance attestation provenance

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

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.

v29.7.0

1 finding

LOW No provenance attestation provenance

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

v29.6.4

1 finding

LOW No provenance attestation provenance

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

v29.6.3

1 finding

LOW No provenance attestation provenance

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

v29.6.2

1 finding

LOW No provenance attestation provenance

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

v29.6.1

1 finding

LOW No provenance attestation provenance

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

v29.6.0

1 finding

LOW No provenance attestation provenance

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

v29.5.0

1 finding

LOW No provenance attestation provenance

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

v29.4.3

1 finding

LOW No provenance attestation provenance

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

v29.4.2

1 finding

LOW No provenance attestation provenance

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

v29.4.1

1 finding

LOW No provenance attestation provenance

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

v29.4.0

1 finding

LOW No provenance attestation provenance

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

v29.3.1

1 finding

LOW No provenance attestation provenance

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

v29.3.0

1 finding

LOW No provenance attestation provenance

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

v29.2.2

1 finding

LOW No provenance attestation provenance

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

v29.2.1

1 finding

LOW No provenance attestation provenance

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

v29.2.0

1 finding

LOW No provenance attestation provenance

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

v29.1.2

1 finding

LOW No provenance attestation provenance

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

v29.1.1

1 finding

LOW No provenance attestation provenance

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

v29.1.0

1 finding

LOW No provenance attestation provenance

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

v29.0.3

1 finding

LOW No provenance attestation provenance

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

v29.0.2

1 finding

LOW No provenance attestation provenance

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

v29.0.1

1 finding

LOW No provenance attestation provenance

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

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

v28.1.3

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2022-07-13) provenance

This version was published by a different npm account than previous versions on 2022-07-13. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v28.1.2

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2022-06-29) provenance

This version was published by a different npm account than previous versions on 2022-06-29. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v28.1.1

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2022-06-07) provenance

This version was published by a different npm account than previous versions on 2022-06-07. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v28.1.0

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2022-05-06) provenance

This version was published by a different npm account than previous versions on 2022-05-06. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v28.0.2

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2022-04-27) provenance

This version was published by a different npm account than previous versions on 2022-04-27. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v28.0.1

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2022-04-26) provenance

This version was published by a different npm account than previous versions on 2022-04-26. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v28.0.0

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2022-04-25) provenance

This version was published by a different npm account than previous versions on 2022-04-25. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v27.5.1

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2022-02-08) provenance

This version was published by a different npm account than previous versions on 2022-02-08. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v27.5.0

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2022-02-05) provenance

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

LOW No provenance attestation provenance

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

v27.4.6

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2022-01-04) provenance

This version was published by a different npm account than previous versions on 2022-01-04. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v27.4.2

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2021-11-30) provenance

This version was published by a different npm account than previous versions on 2021-11-30. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v27.4.1

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2021-11-30) provenance

This version was published by a different npm account than previous versions on 2021-11-30. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v27.4.0

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2021-11-29) provenance

This version was published by a different npm account than previous versions on 2021-11-29. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v27.3.1

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2021-10-19) provenance

This version was published by a different npm account than previous versions on 2021-10-19. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v27.3.0

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2021-10-17) provenance

This version was published by a different npm account than previous versions on 2021-10-17. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v27.2.5

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2021-10-08) provenance

This version was published by a different npm account than previous versions on 2021-10-08. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v27.2.4

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2021-09-29) provenance

This version was published by a different npm account than previous versions on 2021-09-29. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v27.2.3

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2021-09-28) provenance

This version was published by a different npm account than previous versions on 2021-09-28. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v27.2.2

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2021-09-25) provenance

This version was published by a different npm account than previous versions on 2021-09-25. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v27.2.0

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2021-09-13) provenance

This version was published by a different npm account than previous versions on 2021-09-13. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v27.1.1

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2021-09-08) provenance

This version was published by a different npm account than previous versions on 2021-09-08. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v27.1.0

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2021-08-27) provenance

This version was published by a different npm account than previous versions on 2021-08-27. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v27.0.6

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2021-06-28) provenance

This version was published by a different npm account than previous versions on 2021-06-28. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v27.0.5

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2021-06-22) provenance

This version was published by a different npm account than previous versions on 2021-06-22. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v27.0.3

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2021-05-29) provenance

This version was published by a different npm account than previous versions on 2021-05-29. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v27.0.2

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2021-05-29) provenance

This version was published by a different npm account than previous versions on 2021-05-29. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v27.0.1

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2021-05-25) provenance

This version was published by a different npm account than previous versions on 2021-05-25. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v27.0.0

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2021-05-25) provenance

This version was published by a different npm account than previous versions on 2021-05-25. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v26.6.2

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2020-11-02) provenance

This version was published by a different npm account than previous versions on 2020-11-02. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v26.6.1

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2020-10-23) provenance

This version was published by a different npm account than previous versions on 2020-10-23. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v26.6.0

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2020-10-19) provenance

This version was published by a different npm account than previous versions on 2020-10-19. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v26.5.2

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2020-10-06) provenance

This version was published by a different npm account than previous versions on 2020-10-06. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v26.5.0

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2020-10-05) provenance

This version was published by a different npm account than previous versions on 2020-10-05. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v26.3.0

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2020-08-10) provenance

This version was published by a different npm account than previous versions on 2020-08-10. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v26.2.0

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2020-07-30) provenance

This version was published by a different npm account than previous versions on 2020-07-30. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v26.1.0

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2020-06-23) provenance

This version was published by a different npm account than previous versions on 2020-06-23. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v26.0.1

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2020-05-05) provenance

This version was published by a different npm account than previous versions on 2020-05-05. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v26.0.0

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2020-05-04) provenance

This version was published by a different npm account than previous versions on 2020-05-04. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v25.5.0

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2020-04-28) provenance

This version was published by a different npm account than previous versions on 2020-04-28. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v25.4.0

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2020-04-19) provenance

This version was published by a different npm account than previous versions on 2020-04-19. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v25.3.0

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2020-04-08) provenance

This version was published by a different npm account than previous versions on 2020-04-08. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v25.2.6

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2020-04-02) provenance

This version was published by a different npm account than previous versions on 2020-04-02. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v25.2.4

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2020-03-29) provenance

This version was published by a different npm account than previous versions on 2020-03-29. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v25.2.3

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2020-03-26) provenance

This version was published by a different npm account than previous versions on 2020-03-26. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v25.2.1

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2020-03-26) provenance

This version was published by a different npm account than previous versions on 2020-03-26. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v25.2.0

2 findings

HIGH Publisher changed: scotthovestadt → simenb (on 2020-03-25) provenance

This version was published by a different npm account than previous versions on 2020-03-25. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v25.1.0

2 findings

HIGH Publisher changed: scotthovestadt → davidzilburg (on 2020-01-22) provenance

This version was published by a different npm account than previous versions on 2020-01-22. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v25.0.0

1 finding

LOW No provenance attestation provenance

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

v24.9.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.

v24.8.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.

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

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

v24.6.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.

v24.5.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.

v24.3.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.