Is Ink Safe?
Yes, Ink is safe to use. Ink is a Node.js package with a Nerq Trust Score of 78.8/100 (B+), based on 3 independent data dimensions. It is recommended for production use. Security: 90/100. Popularity: 90/100. Data sourced from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-03-29. Machine-readable data (JSON).
Is Ink safe?
YES — Ink has a Nerq Trust Score of 78.8/100 (B+). It meets Nerq's trust threshold with strong signals across security, maintenance, and community adoption. Recommended for production use — review the full report below for specific considerations.
Trust Score Breakdown
Key Findings
Details
| Author | vdemedes |
| Category | npm |
| Source | N/A |
Ink Across Platforms
Same developer/company in other registries:
Safety Guide: Ink
What is Ink?
Ink is a Node.js package — React for CLI.
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=ink
Key Safety Concerns for Node.js packages
When evaluating any Node.js package, watch for: dependency vulnerabilities, malicious packages, typosquatting.
Trust Assessment
Ink has a Nerq Trust Score of 79/100 (B+) and meets Nerq trust threshold. This score is based on automated analysis of security, maintenance, community, and quality signals.
Key Takeaways
- Ink has a Trust Score of 79/100 (B+).
- Recommended for use — passes trust threshold.
- Always verify independently using the Nerq API.
Frequently Asked Questions
Is Ink safe to use?
What is Ink's trust score?
What are safer alternatives to Ink?
Does Ink have known vulnerabilities?
How actively maintained is Ink?
Popular in npm
Browse Categories
Disclaimer: Nerq trust scores are automated assessments based on publicly available signals. They are not endorsements or guarantees. Always conduct your own due diligence.