Is Commonmark Safe?
Commonmark — Nerq Trust Score 53.2/100 (C- grade). Score based on 2 independent trust signals. with 6 known vulnerabilities Last analyzed: 2026-04-12
Commonmark is a PHP package with a Nerq Trust Score of 53.2/100 (C-), based on 3 independent data dimensions. Last analyzed: 2026-04-12 Security: 50/100. Popularity: 100/100. Data sourced from packagist.org, GitHub, and NVD. Last updated: 2026-04-12. Machine-readable data (JSON).
Is Commonmark safe?
Trust Score Breakdown — Commonmark has a Nerq Trust Score of 53.2/100 (C-). Measured across 2 independent trust signals (as of 2026-04-12).
What is Commonmark's trust score?
Commonmark has a Nerq Trust Score of 53.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 Commonmark?
Commonmark's strongest signal is popularity at 100/100. 6 known vulnerabilities were identified.
What is Commonmark and who maintains it?
| Author | league |
| Category | PHP Packages |
| Stars | 2,980 |
| Source | N/A |
Similar Packagist by Trust Score
Compare
Safety Guide: Commonmark
What is Commonmark?
Commonmark is a PHP package — Highly-extensible PHP Markdown parser which fully supports the CommonMark spec and GitHub-Flavored Markdown (GFM).
How to Verify Safety
Run composer audit. Check packagist.org.
You can also check the trust score via API: GET /v1/preflight?target=league/commonmark
Key Safety Concerns for PHP package
When evaluating any PHP package, watch for: dependency vulnerabilities, PHP compatibility.
Measured Signals
Commonmark has a Nerq Trust Score of 53/100 (C-). This score is a composite of automated measurements of security, maintenance, community, and quality signals.
Key Takeaways
- Commonmark has a Trust Score of 53/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 | 50/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 Commonmark collect?
Commonmark is a PHP package maintained by league. It receives approximately 401,366,510 weekly downloads.
As a development package, Commonmark 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: Commonmark Privacy Report · Privacy review
Is Commonmark secure?
Security score: 50/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: Commonmark Security Report
How we calculated this score
Commonmark's trust score of 53.2/100 (C-) is computed from packagist.org, GitHub, and NVD. The score reflects 5 independent dimensions: security (50/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 Commonmark Safe?
What is Commonmark's trust score?
What are safer alternatives to Commonmark?
Does Commonmark have known vulnerabilities?
Is Commonmark 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.