Is O O Safe?
O O has significant trust concerns. O O is a Node.js package (o_o: A simple HTTP/HTTPS proxy server) with a Nerq Trust Score of 23.0/100 (F). It is below the recommended threshold of 70. Data sourced from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-03-24. Machine-readable data (JSON).
Is O O safe?
NO — USE WITH CAUTION — O O has a Nerq Trust Score of 23.0/100 (F). 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.
Trust Score Breakdown
Key Findings
Details
| Author | jacksontian |
| Category | npm |
| Source | N/A |
O O Across Platforms
Same developer/company in other registries:
Safety Guide: O O
What is O O?
O O is a Node.js package — o_o: A simple HTTP/HTTPS proxy server.
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=o_o
Key Safety Concerns for Node.js packages
When evaluating any Node.js package, watch for: dependency vulnerabilities, malicious packages, typosquatting.
Trust Assessment
O O has a Nerq Trust Score of 23/100 (F) 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
- O O has a Trust Score of 23/100 (F).
- Review carefully before use — below trust threshold.
- Always verify independently using the Nerq API.
Frequently Asked Questions
Is O O safe to use?
What is O O's trust score?
What are safer alternatives to O O?
Does O O have known vulnerabilities?
How actively maintained is O O?
Disclaimer: Nerq trust scores are automated assessments based on publicly available signals. They are not endorsements or guarantees. Always conduct your own due diligence.