You are browsing the Symfony 4 documentation, which changes significantly from Symfony 3.x. If your app doesn't use Symfony 4 yet, browse the Symfony 3.4 documentation.
How to Check for Known Security Vulnerabilities in Your Dependencies
How to Check for Known Security Vulnerabilities in Your Dependencies¶
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
security:check that checks your
file to find known security vulnerabilities in your installed dependencies:
$ symfony security:check
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 cloning the security advisories database published
by the FriendsOfPHP organization, so your
composer.lock file is not sent on
security:check 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.
This work, including the code samples, is licensed under a Creative Commons BY-SA 3.0 license.