phpwarden vs. Roave Security Advisories
roave/security-advisories is a Composer package that refuses to install dependency versions with known advisories. phpwarden scans what is already installed, across the PHP engine, Composer and WordPress, ranked by exploitation. They work well together.
Short version: Use both. Roave Security Advisories stops a known-vulnerable
package version from being installed at
composer require or composer update time, with zero
runtime cost and nothing to run. phpwarden tells you what is vulnerable in what you already have, including the PHP
engine and WordPress, which a Composer conflict list cannot see, and ranks it by real-world exploitation.Feature comparison
| roave/security-advisories | phpwarden | |
|---|---|---|
| Blocks installing known-vulnerable Composer versions | ✓ at require / update time | ✗ reports; CI exit code can fail a build |
| Zero runtime, no tool to run | ✓ Yes | ✗ a CLI you run, or CI |
| Checks an existing composer.lock on install | ✗ composer install from a lock file is not checked | ✓ phpwarden deps composer.lock |
| PHP engine version CVEs | ✗ No | ✓ Yes |
| WordPress core / plugins / themes | ✗ No | ✓ Yes |
| Exploitation ranking (CISA KEV, then EPSS, then CVSS) | ✗ No | ✓ Yes |
| Reachability | ✗ No | ✓ Composer |
| Scans your own code | ✗ No | ✓ 89 rules, whole program |
| Data sources | FriendsOfPHP and GitHub Advisory Database | OSV, NVD, FriendsOfPHP, php-src NEWS, CISA KEV, FIRST EPSS |
| License | ✓ MIT | ✓ Apache-2.0 |
| Cost | Free | Free; Pro $39/mo; Team $149/mo |
Where Roave Security Advisories is stronger
- Prevention at the source. It works through Composer's conflict rules, so a vulnerable version simply will not resolve. Nothing to schedule, no output to read.
- Zero runtime. Its README says it provides no API or usable classes; it only blocks installs.
- Frequent data. It is rebuilt from FriendsOfPHP and the GitHub Advisory Database on a frequent schedule.
Where phpwarden differs
- What is already deployed. Roave only acts on require and update; a deploy that runs
composer installfrom a lock file is not checked.phpwarden deps composer.lockchecks the lock file you ship, and flags advisories published after you installed. - Beyond Composer. The PHP engine per branch and WordPress, which are outside Composer's dependency graph.
- Priorities, not just a block. When an advisory lands on something you already run, phpwarden ranks it by CISA KEV, then EPSS (54 known exploited of about 19,500 distinct vulnerabilities) and checks whether your code uses the package.
How to use them together
composer require --dev roave/security-advisories:dev-latest # block vulnerable installs
composer require --dev phpwarden/phpwarden # scan what is installed
vendor/bin/phpwarden deps composer.lock
Try phpwarden on your project
Zero dependencies, offline, Apache-2.0. Ranks findings by CISA KEV → EPSS → CVSS.
composer require --dev phpwarden/phpwarden # PHP projects → vendor/bin/phpwarden
vendor/bin/phpwarden deps composer.lock # Composer
vendor/bin/phpwarden scan # PHP engine on this host
vendor/bin/phpwarden wordpress /var/www/html # WordPress core, plugins, themes
No Composer? pipx install phpwarden or the single-file phpwarden.pyz. In CI: oroma-alfred/phpwarden-action@v1.
About this comparison
- Roave/SecurityAdvisories (GitHub README: purpose, data sources, when checks run, MIT)
- roave/security-advisories on Packagist
- phpwarden pricing: Free ($0: CLI, bundled feed, free weekly feed updates, one dashboard project); Pro $39/month (maintained feed rebuilt twice a day, up to 25 projects, weekly live check of each verified site, alerts); Team $149/month (unlimited projects, client reports with your logo, view-only client logins, 5 staff seats, partner API).