Skip to content

Renamed the security:check command as check:security #12143

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 13, 2019
Merged

Renamed the security:check command as check:security #12143

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions contributing/code/security.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,8 @@ confirmed, the core team works on a solution following these steps:
#. Publish the post on the official Symfony `blog`_ (it must also be added to
the "`Security Advisories`_" category);
#. Update the public `security advisories database`_ maintained by the
FriendsOfPHP organization and which is used by the ``security:check`` command.
FriendsOfPHP organization and which is used by
:doc:`the check:security command </security/security_checker>`.

.. note::

Expand Down Expand Up @@ -169,7 +170,7 @@ Security Advisories
.. tip::

You can check your Symfony application for known security vulnerabilities
using the ``security:check`` command (see :doc:`/security/security_checker`).
using the ``check:security`` command (see :doc:`/security/security_checker`).

Check the `Security Advisories`_ blog category for a list of all security
vulnerabilities that were fixed in Symfony releases, starting from Symfony
Expand Down
6 changes: 3 additions & 3 deletions security/security_checker.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,12 +6,12 @@ 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 :doc:`Symfony local server </setup/symfony_server>`
includes a command called ``security:check`` that checks your ``composer.lock``
includes a command called ``check:security`` that checks your ``composer.lock``
file to find known security vulnerabilities in your installed dependencies:

.. code-block:: terminal

$ symfony security:check
$ 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
Expand All @@ -21,7 +21,7 @@ the network.

.. tip::

The ``security:check`` command terminates with a non-zero exit code if
The ``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.
Expand Down