Is Chron Safe?

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

Exercise caution with Chron. Chron is a npm package with a Nerq Trust Score of 46.2/100 (D), based on 3 independent data dimensions. 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-03-25. Machine-readable data (JSON).

Is Chron safe?

NO — USE WITH CAUTION — Chron 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 → Chron Privacy Report →

What is Chron's trust score?

Chron 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 Chron?

Chron'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 Chron and who maintains it?

Authordresende
Categorynpm Packages
SourceN/A

Chron Across Platforms

Same developer/company in other registries:

chron
57/100 · crates
chron
46/100 · pypi
Chron
46/100 · nuget

Similar Npm by Trust Score

create-sss (56)sysdb (56)better-auth-lead (56)@typeserve/core (56)happy-translate (56)
See all safest Npm →

Compare

Chron vs create-sssChron vs sysdbChron vs better-auth-lead

Safety Guide: Chron

What is Chron?

Chron is a Node.js package — Task scheduler.

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

Key Safety Concerns for Node.js package

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

Trust Assessment

Chron 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 Chron Safe?
Exercise caution. chron with 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 Chron's trust score?
chron: 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=chron
What are safer alternatives to Chron?
In the npm Packages category, more Node.js packages are being analyzed — check back soon. chron scores 46.2/100.
Does Chron have known vulnerabilities?
Nerq checks Chron 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.
Is Chron actively maintained?
Chron maintenance score: N/A. Check the repository for recent commit activity and issue responsiveness.
API: /v1/preflight Trust Badge API Docs

See Also

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