Is Ben Safe?
Ben — Nerq Trust Score 48.2/100 (D grade). Based on analysis of 2 trust dimensions, it is has notable safety concerns. Last updated: 2026-07-11.
Exercise caution with Ben. Ben is a npm package with a Nerq Trust Score of 48.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 Ben safe?
NO — USE WITH CAUTION — Ben has a Nerq Trust Score of 48.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.
What is Ben's trust score?
Ben 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.
What are the key security findings for Ben?
Ben'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+.
What is Ben and who maintains it?
| Author | Unknown |
| Category | npm Packages |
| Source | N/A |
Ben Across Platforms
Same developer/company in other registries:
Similar Npm by Trust Score
Safety Guide: Ben
What is Ben?
Ben is a Node.js package — simple timing benchmarks for synchronous and asynchronous code.
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=ben
Key Safety Concerns for Node.js package
When evaluating any Node.js package, watch for: dependency vulnerabilities, malicious packages, typosquatting.
Trust Assessment
Ben has a Nerq Trust Score of 48/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
- Ben has a Trust Score of 48/100 (D).
- Review carefully before use — below trust threshold.
- Always verify independently using the Nerq API.
Frequently Asked Questions
Is Ben Safe?
What is Ben's trust score?
What are safer alternatives to Ben?
Does Ben have known vulnerabilities?
Is Ben actively maintained?
Popular in npm Packages
Browse Categories
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.