Is Fake Timers Safe?

Fake Timers — Nerq Trust Score 81.0/100 (A- grade). Based on analysis of 2 trust dimensions, it is considered safe to use. Last updated: 2026-04-03.

Yes, Fake Timers is safe to use. Fake Timers is a Node.js package with a Nerq Trust Score of 81.0/100 (A-), based on 3 independent data dimensions. It is recommended for production use. Security: 90/100. Popularity: 100/100. Data sourced from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-04-03. Machine-readable data (JSON).

Is Fake Timers safe?

YES — Fake Timers has a Nerq Trust Score of 81.0/100 (A-). It meets Nerq's trust threshold with strong signals across security, maintenance, and community adoption. Recommended for production use — review the full report below for specific considerations.

Security Analysis → {name} Privacy Report →

What is Fake Timers's trust score?

Fake Timers has a Nerq Trust Score of 81.0/100, earning a A- grade. This score is based on 2 independently measured dimensions including security, maintenance, and community adoption.

Security
90
Popularity
100

What are the key security findings for Fake Timers?

Fake Timers's strongest signal is popularity at 100/100. No known vulnerabilities have been detected. It meets the Nerq Verified threshold of 70+.

Security score: 90/100 (strong)
Popularity: 100/100 — community adoption

What is Fake Timers and who maintains it?

Authormrgnrdrck
Categorynpm
SourceN/A

Similar Npm by Trust Score

@testing-library/react (90)@supabase/realtime-js (90)@supabase/supabase-js (90)@supabase/storage-js (90)@supabase/functions-js (90)
See all safest Npm →

Compare

Fake Timers vs @testing-library/reactFake Timers vs @supabase/realtime-jsFake Timers vs @supabase/supabase-js

Safety Guide: Fake Timers

What is Fake Timers?

Fake Timers is a Node.js package — Fake JavaScript timers.

How to Verify Safety

Run npm audit to check for vulnerabilities. Review the package's GitHub repository for recent commits.

You can also check the trust score via API: GET /v1/preflight?target=@sinonjs/fake-timers

Key Safety Concerns for Node.js packages

When evaluating any Node.js package, watch for: dependency vulnerabilities, malicious packages, typosquatting.

Trust Assessment

Fake Timers has a Nerq Trust Score of 81/100 (A-) and meets Nerq trust threshold. This score is based on automated analysis of security, maintenance, community, and quality signals.

Key Takeaways

Detailed Score Analysis

DimensionScore
Security90/100
Privacy80/100
Reliability90/100
Transparency85/100
Maintenance60/100

Based on 5 dimensions. Data from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard.

What data does Fake Timers collect?

Fake Timers is a Node.js package maintained by mrgnrdrck. It receives approximately 49,312,523 weekly downloads. Licensed under BSD-3-Clause.

As a development package, Fake Timers does not directly collect end-user personal data. However, applications built with it may collect data depending on implementation. Privacy score: 80/100.

Review the package's dependencies for potential supply chain risks. Run your package manager's audit command regularly.

Full analysis: Fake Timers Privacy Report · Privacy review

Is Fake Timers secure?

Security score: 90/100. Fake Timers has 0 known vulnerabilities (CVEs) in the National Vulnerability Database. This is a clean record.

Licensed under BSD-3-Clause, allowing code inspection. Open-source packages allow independent security review of the source code.

Run your package manager's audit command (`npm audit`, `pip audit`, `cargo audit`) to check for known vulnerabilities in your dependency tree.

Full analysis: Fake Timers Security Report

How we calculated this score

Fake Timers's trust score of 81.0/100 (A-) is computed from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. The score reflects 5 independent dimensions: security (90/100), privacy (80/100), reliability (90/100), transparency (85/100), maintenance (60/100). Each dimension is weighted equally to produce the composite trust score.

Nerq analyzes over 7.5 million entities across 26 registries using the same methodology, enabling direct cross-entity comparison. Scores are updated continuously as new data becomes available.

This page was last reviewed on April 03, 2026. Data version: 1.0.

Full methodology documentation · Machine-readable data (JSON API)

Frequently Asked Questions

Is Fake Timers safe to use?
Yes, it is safe to use. @sinonjs/fake-timers has a Nerq Trust Score of 81.0/100 (A-). Strongest signal: popularity (100/100). Score based on security (90/100), popularity (100/100).
What is Fake Timers's trust score?
@sinonjs/fake-timers: 81.0/100 (A-). Score based on: security (90/100), popularity (100/100). Scores update as new data becomes available. API: GET nerq.ai/v1/preflight?target=@sinonjs/fake-timers
What are safer alternatives to Fake Timers?
In the npm category, more Node.js packages are being analyzed — check back soon. @sinonjs/fake-timers scores 81.0/100.
Does Fake Timers have known vulnerabilities?
Nerq checks Fake Timers against NVD, OSV.dev, and registry-specific vulnerability databases. Current security score: 90/100. Run your package manager's audit command for the latest findings.
How actively maintained is Fake Timers?
Fake Timers has a trust score of 81.0/100 (A-). Meets Nerq Verified threshold.
API: /v1/preflight Trust Badge API Docs

Disclaimer: Nerq trust scores are automated assessments based on publicly available signals. They are not endorsements or guarantees. Always conduct your own due diligence.

We use cookies for analytics and caching. Privacy Policy