Is Complexity Safe?
Complexity — Nerq Trust Score 63.2/100 (C+ grade). Score based on 2 independent trust signals. Last analyzed: 2026-04-12
Complexity is a PHP package with a Nerq Trust Score of 63.2/100 (C+), based on 3 independent data dimensions. Last analyzed: 2026-04-12 Security: 90/100. Popularity: 100/100. Data sourced from packagist.org, GitHub, and NVD. Last updated: 2026-04-12. Machine-readable data (JSON).
Is Complexity safe?
Trust Score Breakdown — Complexity has a Nerq Trust Score of 63.2/100 (C+). Measured across 2 independent trust signals (as of 2026-04-12).
What is Complexity's trust score?
Complexity has a Nerq Trust Score of 63.2/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 Complexity?
Complexity's strongest signal is popularity at 100/100. No known vulnerabilities have been detected.
What is Complexity and who maintains it?
| Author | sebastian |
| Category | PHP Packages |
| Stars | 1,255 |
| Source | N/A |
Complexity Across Platforms
Same developer/company in other registries:
Similar Packagist by Trust Score
Compare
Safety Guide: Complexity
What is Complexity?
Complexity is a PHP package — Library for calculating the complexity of PHP code units.
How to Verify Safety
Run composer audit. Check packagist.org.
You can also check the trust score via API: GET /v1/preflight?target=sebastian/complexity
Key Safety Concerns for PHP package
When evaluating any PHP package, watch for: dependency vulnerabilities, PHP compatibility.
Measured Signals
Complexity has a Nerq Trust Score of 63/100 (C+). This score is a composite of automated measurements of security, maintenance, community, and quality signals.
Key Takeaways
- Complexity has a Trust Score of 63/100 (C+).
- The score is a measured composite — it is not a suitability judgment. Evaluate the individual signals against your own requirements.
- Query the current measured values via the Nerq API.
Detailed Score Analysis
| Dimension | Score |
|---|---|
| Security | 90/100 |
| Maintenance | 50/100 |
| Popularity | 100/100 |
| Quality | 40/100 |
| Community | 35/100 |
Based on 5 dimensions. Data from packagist.org, GitHub, and NVD.
What data does Complexity collect?
Complexity is a PHP package maintained by sebastian. It receives approximately 525,863,210 weekly downloads.
As a development package, Complexity 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: Complexity Privacy Report · Privacy review
Is Complexity secure?
Security score: 90/100 (0-100, higher = fewer measured security issues).
Nerq monitors this entity against NVD, OSV.dev, and registry-specific vulnerability databases for ongoing security assessment.
Full analysis: Complexity Security Report
Complexity Across Platforms
Same developer/company in other registries:
How we calculated this score
Complexity's trust score of 63.2/100 (C+) is computed from packagist.org, GitHub, and NVD. The score reflects 5 independent dimensions: security (90/100), maintenance (50/100), popularity (100/100), quality (40/100), community (35/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.
Signals last measured on April 12, 2026. Data version: 1.0.
Full methodology documentation · Machine-readable data (JSON API)
Frequently Asked Questions
Is Complexity Safe?
What is Complexity's trust score?
What are safer alternatives to Complexity?
Does Complexity have known vulnerabilities?
Is Complexity actively maintained?
Popular in PHP Packages
See Also
Disclaimer: Nerq trust scores are automated measurements based on publicly available signals. They are not endorsements, verdicts, or guarantees of suitability. Always evaluate the signals against your own requirements.