Snyk helps you find, fix and monitor for known vulnerabilities in your dependencies, both on an ad hoc basis and as part of your CI (Build) system.
This plugin provides dependency metadata for Gradle projects that use gradle
and have a build.gradle
file.
❓No issues expected but test not updated yet to verify ✅Supported and verified with tests
OS | Supported |
---|---|
Windows | ✅ |
Linux | ✅ |
OSX | ✅ |
Node | Supported |
---|---|
6 | ✅ |
8 | ✅ |
10 | ✅ |
12 | ❓ |
Java / Gradle | 2.* | 3.* | 4.* | 5.* |
---|---|---|---|---|
8 | ✅ | ✅ | ✅ | ✅ |
9 | ✅ | ✅ | ✅ | ✅ |
10 | ✅ | ✅ | ✅ | ✅ |
11 | ✅ | ✅ | ✅ | ✅ |
13 | ❓ | ❓ | ❓ | ❓ |
--gradle-sub-project=foo
return dependencies for a specific subproject (by default, return only the dependencies for the top-level project)
Additional command line arguments:
-
--all-sub-projects
for "multi project" configurations, test all sub-projects. -
--configuration-matching=<string>
Resolve dependencies using only configuration(s) that match the provided Java regular expression, e.g. '^releaseRuntimeClasspath$'. -
--configuration-attributes=<string>
Select certain values of configuration attributes to resolve the dependencies. E.g.: 'buildtype:release,usage:java-runtime'
See lib/init.gradle
for the Groovy script injected in Gradle builds to gather and resolve the dependencies.