@sinonjs/fake-timers
Fake JavaScript timers
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 | missing-githead | AI (provenance): Alpha pre-release published by a long-standing trusted maintainer (fatso83, 419/0 record). Missing gitHead is consistent with a local publish during development, not a security concern for this package. | ai | |
| provenance | publisher-changed | AI (provenance): simenb is a long-standing sinonjs ecosystem maintainer (910 approved packages, 3048 days on npm); the fatso83→simenb transition is a legitimate org-level handoff, not a compromise. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): eval() is used to execute string-form timer callbacks, mirroring the browser/Node.js setTimeout/setInterval spec. This is intentional and documented behavior for a fake timer library, not a supply-chain risk. | ai | |
| dependencies | unvetted-dep:@sinonjs/commons | AI (dependencies): @sinonjs/commons is a first-party sinonjs utility dependency, stable and expected for all versions of this package. | ai | |
| provenance | no-provenance | AI (provenance): Lack of provenance is common across npm; no other risk signals present to elevate this concern for this package. | ai |
Versions (showing 49 of 49)
| Version | Deps | Published |
|---|---|---|
| 15.4.0 | 1 / 15 | |
| 15.3.2 | 1 / 15 | |
| 15.3.1 | 1 / 14 | |
| 15.3.0 | 1 / 14 | |
| 15.2.2 | 1 / 12 | |
| 15.2.1 | 1 / 12 | |
| 15.2.0 | 1 / 12 | |
| 15.1.2 | 1 / 12 | |
| 15.1.1 | 1 / 12 | |
| 15.1.0 | 1 / 12 | |
| 15.0.0 | 1 / 12 | |
| 14.0.0 | 1 / 12 | |
| 13.0.5 | 1 / 12 | |
| 13.0.4 | 1 / 12 | |
| 13.0.3 | 1 / 12 | |
| 13.0.2 | 1 / 12 | |
| 13.0.1 | 1 / 12 | |
| 13.0.0 | 1 / 12 | |
| 12.0.0 | 1 / 12 | |
| 11.3.1 | 1 / 12 | |
| 11.3.0 | 1 / 12 | |
| 11.2.2 | 1 / 9 | |
| 11.2.1 | 1 / 9 | |
| 11.2.0 | 1 / 9 | |
| 11.1.0 | 1 / 9 | |
| 11.0.0 | 1 / 9 | |
| 10.3.0 | 1 / 9 | |
| 10.2.0 | 1 / 9 | |
| 10.1.0 | 1 / 9 | |
| 10.0.2 | 1 / 9 | |
| 10.0.1 | 1 / 9 | |
| 10.0.0 | 1 / 11 | |
| 9.1.2 | 1 / 11 | |
| 9.1.1 | 1 / 11 | |
| 9.1.0 | 1 / 11 | |
| 9.0.0 | 1 / 11 | |
| 8.1.0 | 1 / 11 | |
| 8.0.1 | 1 / 11 | |
| 8.0.0 | 1 / 9 | |
| 7.1.2 | 1 / 16 | |
| 7.1.1 | 1 / 16 | |
| 7.1.0 | 1 / 16 | |
| 7.0.5 | 1 / 15 | |
| 7.0.4 | 1 / 15 | |
| 7.0.2 | 1 / 15 | |
| 7.0.1 | 1 / 15 | |
| 7.0.0 | 1 / 15 | |
| 6.0.1 | 1 / 16 | |
| 6.0.0 | 1 / 16 |
v15.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.0
2 findingsThis version was published by a different npm account than previous versions on 2022-11-08. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.1
2 findingsThis version was published by a different npm account than previous versions on 2022-03-05. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
2 findingsThis version was published by a different npm account than previous versions on 2022-01-28. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.