This project is not covered by Drupal’s security advisory policy.
Tells you which Composer patches you can drop, which contributed projects need a look, and which PHP libraries have known security problems.
Patches get old quietly. An issue gets fixed, the fix ships, and the patch stays in composer.json until an update breaks on it. Merge request URLs have the opposite problem: new commits reach your site on the next composer update, and nobody reads them first.
Patches
Dependency Health reads your patches from patches.lock.json, composer.json or patches.json, finds the issue or merge request behind each one, and says what to do:
- Already in your version. Remove the patch.
- In release 1.14.0. Update, then remove the patch.
- Merged, not in a newer release yet. Keep the patch for now.
- Still open. Keep the patch.
- Closed without a fix. Check if you still need the patch.
- The package is not installed. Remove the patch.
When a patch can go, a "How" box gives the entry to delete and the Composer commands to run. It also warns about patch URLs that can change and patches downloaded over plain HTTP.
Contributed projects
For each project you get the last release, security coverage and maintenance status. It flags projects that are abandoned or looking for a new maintainer, versions outside security coverage, branches that are no longer supported, versions that are not in the release list, and projects you downloaded but never enabled.
PHP libraries
Symfony, Guzzle, Twig and the rest of your vendor folder are checked against the security advisories on packagist.org, the data behind composer audit. Update Manager does not cover them. A vulnerable version turns the status report red and comes with the command to update it.
Ignore, with a reason
Keeping a patch on purpose? Ignore it and write why. It stops counting until what the report says about it changes. Ignores live in configuration, so the whole team shares them.
Where to find it
- Reports > Dependency health
- The status report, which warns when something needs attention
- An email, once for each new problem
- Drush:
dependency-health:check,:patches,:projectsand:libraries, with--format=jsonfor pipelines
Post-installation
Give "View dependency health" to the roles that read the report, and "Administer dependency health" to the ones that may ignore items and change settings. Go to the report and press "Check now". After that it runs once a week on cron. Email addresses go in Configuration > System > Dependency health.
What your site sends
To drupal.org: project names, issue numbers and merge request numbers. To packagist.org: the names of your PHP libraries, without versions, and you can turn that off. Patches are never downloaded or uploaded, and patch URLs stay on your server.
How exact it is
For a merged merge request, GitLab says which release tags contain the commit, so the answer is exact. A fixed issue only has dates, so that advice is a guess and tells you to check the release notes. The module does not read patches, so it cannot tell you if one still applies.
Project information
- Project categories: Administration tools, Security
- Created by zakariabdc on , updated
This project is not covered by the security advisory policy.
Use at your own risk! It may have publicly disclosed vulnerabilities.

