Is Recurring Date Safe?

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

Recurring Date 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 Recurring Date safe?

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

Security Analysis → Recurring Date Privacy Report →

What is Recurring Date's trust score?

Recurring Date 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 Recurring Date?

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

Authornathanoehlman
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

Recurring Date vs react-library-boilerplate-for-npmRecurring Date vs bindlerRecurring Date vs @yassidev/nuxt-directus

Safety Guide: Recurring Date

What is Recurring Date?

Recurring Date is a Node.js package — Generate a list of dates that meet a given schedule.

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=recurring-date

Key Safety Concerns for Node.js package

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

Measured Signals

Recurring Date 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 Recurring Date Safe?
recurring-date 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 Recurring Date's trust score?
recurring-date: 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=recurring-date
What are safer alternatives to Recurring Date?
In the npm Packages category, more Node.js packages are being analyzed — check back soon. recurring-date scores 48.2/100.
Does Recurring Date have known vulnerabilities?
Nerq checks Recurring Date 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 Recurring Date actively maintained?
Recurring Date 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