How to Check for Known Security Vulnerabilities in Your DependenciesEdit this page
Warning: You are browsing the documentation for Symfony 3.4, which is no longer maintained.
Read the updated version of this page for Symfony 6.3 (the current stable version).
When using lots of dependencies in your Symfony projects, some of them may
contain security vulnerabilities. That's why the Symfony local server
includes a command called
check:security that checks your
file to find known security vulnerabilities in your installed dependencies:
$ symfony check:security
A good security practice is to execute this command regularly to be able to
update or replace compromised dependencies as soon as possible. The security
check is done locally by fetching the security advisories database published
by the FriendsOfPHP organization, so your
composer.lock file is not sent on
check:security command terminates with a non-zero exit code if
any of your dependencies is affected by a known security vulnerability.
This way you can add it to your project build process and your continuous
integration workflows to make them fail when there are vulnerabilities.