fix: Simplify PHP framework suppression for Composer#7693
Merged
jeremylong merged 1 commit intodependency-check:mainfrom May 31, 2025
Merged
fix: Simplify PHP framework suppression for Composer#7693jeremylong merged 1 commit intodependency-check:mainfrom
jeremylong merged 1 commit intodependency-check:mainfrom
Conversation
Contributor
Author
|
This is intentionally filed against |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of Change
The base suppression that is bundled for suppressing
phpin packages names should be expanded, as mentioned in comment by @georgschoelly on #7444.All matches of PHP in Composer packages are safe to consider not being part of PHP framework
cpe:/a:php:phpbecause Composer is the package manager next level down.This change removes three distinct suppressions, which are now covered by the extended regular expression.
Related issues
Have test cases been added to cover the new functionality?
no