Is Lexer Safe?
Lexer — Nerq Trust Score 53.0/100 (C- grade). Based on analysis of 2 trust dimensions, it is has notable safety concerns. Last updated: 2026-03-31.
Use Lexer with some caution. Lexer is a PHP package with a Nerq Trust Score of 53.0/100 (C-), based on 3 independent data dimensions. It is below the recommended threshold of 70. Security: 65/100. Popularity: 95/100. Data sourced from packagist.org, GitHub, and NVD. Last updated: 2026-03-31. Machine-readable data (JSON).
Is Lexer safe?
CAUTION — Lexer has a Nerq Trust Score of 53.0/100 (C-). It has moderate trust signals but shows some areas of concern that warrant attention. Suitable for development use — review security and maintenance signals before production deployment.
What is Lexer's trust score?
Lexer has a Nerq Trust Score of 53.0/100, earning a C- grade. This score is based on 2 independently measured dimensions including security, maintenance, and community adoption.
What are the key security findings for Lexer?
Lexer's strongest signal is popularity at 95/100. No known vulnerabilities have been detected. It has not yet reached the Nerq Verified threshold of 70+.
What is Lexer and who maintains it?
| Author | doctrine |
| Category | packagist |
| Source | N/A |
Similar Packagist by Trust Score
Safety Guide: Lexer
What is Lexer?
Lexer is a PHP package — PHP Doctrine Lexer parser library that can be used in Top-Down, Recursive Descent Parsers..
How to Verify Safety
Run composer audit. Check packagist.org.
You can also check the trust score via API: GET /v1/preflight?target=doctrine/lexer
Key Safety Concerns for PHP packages
When evaluating any PHP package, watch for: dependency vulnerabilities, PHP compatibility.
Trust Assessment
Lexer has a Nerq Trust Score of 53/100 (C-) 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
- Lexer has a Trust Score of 53/100 (C-).
- Review carefully before use — below trust threshold.
- Always verify independently using the Nerq API.
Detailed Score Analysis
| Dimension | Score |
|---|---|
| Security | 65/100 |
| Privacy | 80/100 |
| Reliability | 90/100 |
| Transparency | 50/100 |
| Maintenance | 60/100 |
Based on 5 dimensions. Data from packagist.org, GitHub, and NVD.
What data does Lexer collect?
Lexer is a PHP package maintained by doctrine. It receives approximately 907,056,941 weekly downloads.
As a development package, Lexer does not directly collect end-user personal data. However, applications built with it may collect data depending on implementation. Privacy score: 80/100.
Review the package's dependencies for potential supply chain risks. Run your package manager's audit command regularly.
Full analysis: Lexer Privacy Report · Privacy review
Is Lexer secure?
Security score: 65/100. Review security practices and consider alternatives with higher security scores for sensitive use cases.
Nerq monitors this entity against NVD, OSV.dev, and registry-specific vulnerability databases for ongoing security assessment.
Full analysis: Lexer Security Report
How we calculated this score
Lexer's trust score of 53.0/100 (C-) is computed from packagist.org, GitHub, and NVD. The score reflects 5 independent dimensions: security (65/100), privacy (80/100), reliability (90/100), transparency (50/100), maintenance (60/100). Each dimension is weighted equally to produce the composite trust score.
Nerq analyzes over 7.5 million entities across 26 registries using the same methodology, enabling direct cross-entity comparison. Scores are updated continuously as new data becomes available.
This page was last reviewed on March 31, 2026. Data version: 1.0.
Full methodology documentation · Machine-readable data (JSON API)
Frequently Asked Questions
Is Lexer safe to use?
What is Lexer's trust score?
What are safer alternatives to Lexer?
Does Lexer have known vulnerabilities?
How actively maintained is Lexer?
Popular in packagist
Disclaimer: Nerq trust scores are automated assessments based on publicly available signals. They are not endorsements or guarantees. Always conduct your own due diligence.