Is Cronometer Safe?

Cronometer — Nerq Trust Score 46.2/100 (D grade). Based on analysis of 2 trust dimensions, it is has notable safety concerns. Last updated: 2026-04-01.

Exercise caution with Cronometer. Cronometer is a Node.js package with a Nerq Trust Score of 46.2/100 (D), based on 3 independent data dimensions. It is below the recommended threshold of 70. Security: 90/100. Popularity: 0/100. Data sourced from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-04-01. Machine-readable data (JSON).

Is Cronometer safe?

NO — USE WITH CAUTION — Cronometer has a Nerq Trust Score of 46.2/100 (D). It has below-average trust signals with significant gaps in security, maintenance, or documentation. Not recommended for production use without thorough manual review and additional security measures.

Security Analysis → {name} Privacy Report →

What is Cronometer's trust score?

Cronometer has a Nerq Trust Score of 46.2/100, earning a D grade. This score is based on 2 independently measured dimensions including security, maintenance, and community adoption.

Security
90
Popularity
0

What are the key security findings for Cronometer?

Cronometer's strongest signal is security at 90/100. No known vulnerabilities have been detected. It has not yet reached the Nerq Verified threshold of 70+.

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

What is Cronometer and who maintains it?

AuthorUnknown
Categorynpm
SourceN/A

Similar Npm by Trust Score

@agenticforge/utils (56)xj-rollup-demo (56)esm_002 (56)rollup-start (56)open-antenna (56)
See all safest Npm →

Safety Guide: Cronometer

What is Cronometer?

Cronometer is a Node.js package.

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=cronometer

Key Safety Concerns for Node.js packages

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

Trust Assessment

Cronometer has a Nerq Trust Score of 46/100 (D) and has not yet reached Nerq trust threshold (70+). This score is based on automated analysis of security, maintenance, community, and quality signals.

Key Takeaways

Frequently Asked Questions

Is Cronometer safe to use?
Exercise caution. cronometer has a Nerq Trust Score of 46.2/100 (D). Strongest signal: security (90/100). Score based on security (90/100), popularity (0/100).
What is Cronometer's trust score?
cronometer: 46.2/100 (D). Score based on: security (90/100), popularity (0/100). Scores update as new data becomes available. API: GET nerq.ai/v1/preflight?target=cronometer
What are safer alternatives to Cronometer?
In the npm category, more Node.js packages are being analyzed — check back soon. cronometer scores 46.2/100.
Does Cronometer have known vulnerabilities?
Nerq checks Cronometer 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 Cronometer?
Cronometer has a trust score of 46.2/100 (D). Below Nerq Verified threshold — conduct additional review.
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