Is Recink Safe?

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

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

Is Recink safe?

NO — USE WITH CAUTION — Recink has a Nerq Trust Score of 49.6/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 Recink's trust score?

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

Security
75
Popularity
12

What are the key security findings for Recink?

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

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

What is Recink and who maintains it?

Authormitocgroup
Categorynpm
SourceN/A

Similar Npm by Trust Score

@mui/x-data-grid-premium (60)@syncfusion/ej2-lists (60)stream-chat-react (60)@syncfusion/ej2-notifications (60)@sap/generator-fiori (60)
See all safest Npm →

Safety Guide: Recink

What is Recink?

Recink is a Node.js package — Rethink CI for JavaScript applications.

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

Key Safety Concerns for Node.js packages

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

Trust Assessment

Recink has a Nerq Trust Score of 50/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 Recink safe to use?
Exercise caution. recink has a Nerq Trust Score of 49.6/100 (D). Strongest signal: security (75/100). Score based on security (75/100), popularity (12/100).
What is Recink's trust score?
recink: 49.6/100 (D). Score based on: security (75/100), popularity (12/100). Scores update as new data becomes available. API: GET nerq.ai/v1/preflight?target=recink
What are safer alternatives to Recink?
In the npm category, more Node.js packages are being analyzed — check back soon. recink scores 49.6/100.
Does Recink have known vulnerabilities?
Nerq checks Recink against NVD, OSV.dev, and registry-specific vulnerability databases. Current security score: 75/100. Run your package manager's audit command for the latest findings.
How actively maintained is Recink?
Recink has a trust score of 49.6/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