Scan all unmanaged JAR files
The Snyk CLI can scan unmanaged JAR files in Java applications to identify which open-source package they contain.
The CLI identifies the package name, version, and vulnerabilities only if the package is available in Maven Central, and the JAR file hash matches the hash in Maven Central.
Prerequisite: You must install a supported version of Maven to scan unmanaged JAR files.
Scanning all JAR files in a single folder and scanning each JAR file individually
To scan each JAR file individually, use the following command:
snyk test --scan-unmanaged --file=/path/to/file
When you test each JAR file individually, the name of the JAR file that was scanned appears on the Snyk web UI.
WAR file support: You can scan individual WAR files that are published in Maven Central. To scan open-source dependency JARs directly, you must extract (unzip) all other WAR files or JAR files containing other JARs.
Recursively scanning all subfolders
The method described here is deprecated.
Beginning with Snyk CLI 1.1176.0, by default you can scan all subfolders using the --scan-all-unmanaged
option. When you scan using --scan-all-unmanaged
, the package name appears rather than the file name.
Java apps often have JAR files in a number of different folders within an application.
The following is a Linux/Mac Bash script used with CLI versions before Snyk CLI 1.1176.0 that recurses through all subfolders starting with the current folder and tests each JAR file found.
Setting a value for the REMOTE_REPO_URL
variable is important; it is used to combine all scan results under a single Snyk Project in the UI using the --remote-repo-url
parameter.
The following is a Windows batch script for scanning JARs in all subfolders, run from a scanjar.bat
file.
To use this script, you must have installed the Snyk CLI.
An example follows of the result shown in the Snyk UI after you use these scripts with REMOTE_REPO_URL
set to "econnect".
Last updated