← Home

@jest/fake-timers

npm Repository
51
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
maintainer-change maintainer-removed AI (maintainer-change): Removal of jeanlauliac is consistent with documented Jest team evolution; no takeover indicators. ai
provenance publisher-changed AI (provenance): simenb is a well-known Jest core maintainer; publisher change reflects legitimate Jest team transition, not a compromise. ai
maintainer-change maintainer-added AI (maintainer-change): simenb and davidzilburg are documented Jest core contributors; additions reflect legitimate team changes. ai
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
npm-metadata no-description AI (npm-metadata): Monorepo package with documentation in main Jest repo; missing description is expected. ai
phantom-deps phantom-dep:@jest/types AI (phantom-deps): Framework-scoped Jest package loaded by convention; stable pattern for Jest monorepo packages. ai
phantom-deps phantom-dep:@types/node AI (phantom-deps): Type definitions loaded by convention; stable pattern for Jest monorepo packages. ai
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
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

Versions (showing 51 of 90)

View all versions
Version Deps Published
30.4.1 6 / 1
30.4.0 6 / 1
30.3.0 6 / 2
30.2.0 6 / 2
30.1.2 6 / 2
30.1.1 6 / 2
30.1.0 6 / 2
30.0.5 6 / 2
30.0.4 6 / 2
30.0.2 6 / 2
30.0.1 6 / 2
30.0.0 6 / 2
29.7.0 6 / 2
29.6.4 6 / 2
29.6.3 6 / 2
29.6.2 6 / 2
29.6.1 6 / 2
29.6.0 6 / 2
29.5.0 6 / 2
29.4.3 6 / 2
29.4.2 6 / 2
29.4.1 6 / 2
29.4.0 6 / 2
29.3.1 6 / 2
29.3.0 6 / 2
29.2.2 6 / 2
29.2.1 6 / 2
29.2.0 6 / 2
29.1.2 6 / 2
29.1.1 6 / 2
29.1.0 6 / 2
29.0.3 6 / 2
29.0.2 6 / 2
29.0.1 6 / 2
29.0.0 6 / 2
28.1.3 6 / 2
28.1.2 6 / 2
28.1.1 6 / 2
28.1.0 6 / 2
28.0.2 6 / 2
28.0.1 6 / 2
28.0.0 6 / 2
27.5.1 6 / 1
27.5.0 6 / 2
27.4.6 6 / 2
27.4.2 6 / 2
27.4.1 6 / 2
27.4.0 6 / 2
27.3.1 6 / 2
27.3.0 6 / 2
27.2.5 6 / 2

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.