Is Relative Time Safe?

Relative Time — Nerq Trust Score 48.2/100 (D grade). Score based on 2 independent trust signals. Last analyzed: 2026-03-25

Relative Time is a npm package with a Nerq Trust Score of 48.2/100 (D), based on 3 independent data dimensions. Last analyzed: 2026-03-25 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 Relative Time safe?

Trust Score Breakdown — Relative Time has a Nerq Trust Score of 48.2/100 (D). Measured across 2 independent trust signals (as of 2026-03-25).

Security Analysis → Relative Time Privacy Report →

What is Relative Time's trust score?

Relative Time has a Nerq Trust Score of 48.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 Relative Time?

Relative Time's strongest signal is security at 90/100. No known vulnerabilities have been detected.

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

What is Relative Time and who maintains it?

Authorrxaviers
Categorynpm Packages
SourceN/A

Similar Npm by Trust Score

react-library-boilerplate-for-npm (58)bindler (58)@yassidev/nuxt-directus (58)spectro-kubernetes-client (58)pocketto-svelte (58)
See all safest Npm →

Compare

Relative Time vs react-library-boilerplate-for-npmRelative Time vs bindlerRelative Time vs @yassidev/nuxt-directus

Safety Guide: Relative Time

What is Relative Time?

Relative Time is a Node.js package — Formats JavaScript dates to relative time strings (e.g., "3 hours ago").

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=relative-time

Key Safety Concerns for Node.js package

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

Measured Signals

Relative Time has a Nerq Trust Score of 48/100 (D). This score is a composite of automated measurements of security, maintenance, community, and quality signals.

Key Takeaways

Frequently Asked Questions

Is Relative Time Safe?
relative-time with a Nerq Trust Score of 48.2/100 (D). Strongest signal: security (90/100). Score based on Security (90/100), Popularity (0/100).
What is Relative Time's trust score?
relative-time: 48.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=relative-time
What are safer alternatives to Relative Time?
In the npm Packages category, more Node.js packages are being analyzed — check back soon. relative-time scores 48.2/100.
Does Relative Time have known vulnerabilities?
Nerq checks Relative Time 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 Relative Time actively maintained?
Relative Time 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 measurements based on publicly available signals. They are not endorsements, verdicts, or guarantees of suitability. Always evaluate the signals against your own requirements.

We use cookies for analytics and caching. Privacy