Its got two main areas, the plugin itself in the buildscript and its UTP (Unified Test Platform) in the configurations,
they share some similar dependencies but not idential and because of this some patching might get missed at a component level.
See the build.gradle.kts for code examples.
For a long time I couldn't understand where the extra dependencies kept coming from, including duplicates of the same library but at different versions, for more details ramblings, and where I initially wrote up my findings go read this beercanx/retro-brick-game-raylib#30 (comment)
You should always test and check things, especially after manual security patching as new versions may remove the need for the ducktape patching.
For the plugin you can check what libraries are what version via
./gradlew buildEnvironment | grep 'httpclient'
| | | | \--- org.apache.httpcomponents:httpclient:4.5.12 -> 4.5.14
| | +--- org.apache.httpcomponents:httpclient:4.5.14 (*)
For project depenencies, or custom scopes such as used by UTP, these can be checked via
./gradlew dependencies | grep 'httpclient'
| | | \--- org.apache.httpcomponents:httpclient:4.5.12