lolex
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 | publisher-changed | AI (provenance): mrgnrdrck (Morgan Roderick) is a known sinonjs maintainer with 421 approved packages and 11+ year history. Legitimate org transition. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): eval(timer.func) implements browser-compatible setTimeout(string) behavior — intentional core functionality of a fake-timer library. | ai | |
| provenance | no-provenance | AI (provenance): Published in 2020, before npm provenance/Sigstore existed. Expected for this era of packages. | ai |
Versions (showing 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 6.0.0 | 1 / 16 | |
| 5.1.2 | 1 / 16 | |
| 5.1.1 | 0 / 15 | |
| 5.1.0 | 0 / 15 | |
| 5.0.1 | 0 / 15 | |
| 5.0.0 | 0 / 12 | |
| 4.2.0 | 0 / 12 | |
| 4.1.0 | 0 / 12 | |
| 4.0.1 | 0 / 12 | |
| 3.1.0 | 0 / 12 | |
| 3.0.0 | 0 / 12 | |
| 2.7.5 | 0 / 12 | |
| 2.7.4 | 0 / 12 | |
| 2.7.3 | 0 / 12 | |
| 2.7.2 | 0 / 12 | |
| 2.7.1 | 0 / 13 | |
| 2.7.0 | 0 / 13 | |
| 2.6.0 | 0 / 13 | |
| 2.5.0 | 0 / 13 | |
| 2.4.2 | 0 / 12 | |
| 2.4.1 | 0 / 12 | |
| 2.4.0 | 0 / 12 | |
| 2.3.2 | 0 / 12 | |
| 2.3.1 | 0 / 11 | |
| 2.3.0 | 0 / 11 | |
| 2.2.0 | 0 / 11 | |
| 2.1.3 | 0 / 11 | |
| 2.1.2 | 0 / 11 | |
| 2.1.1 | 0 / 11 | |
| 2.1.0 | 0 / 8 | |
| 2.0.0 | 0 / 8 | |
| 1.6.0 | 0 / 8 | |
| 1.5.2 | 0 / 6 | |
| 1.5.1 | 0 / 6 | |
| 1.5.0 | 0 / 6 | |
| 1.4.0 | 0 / 6 | |
| 1.3.2 | 0 / 6 | |
| 1.3.1 | 0 / 6 | |
| 1.3.0 | 0 / 6 | |
| 1.2.2 | 0 / 6 | |
| 1.2.1 | 0 / 6 | |
| 1.2.0 | 0 / 6 | |
| 1.1.0 | 0 / 5 | |
| 1.0.0 | 0 / 5 |
v6.0.0
2 findingsThis version was published by a different npm account than previous versions on 2020-02-04. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-10-21. This could indicate a legitimate maintainer transition or an account compromise.
v5.1.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-10-14. This could indicate a legitimate maintainer transition or an account compromise.
v5.0.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-10-10. This could indicate a legitimate maintainer transition or an account compromise.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.