All “Core” Scan Options¶
- -n, --processes INTEGER
<input>using n parallel processes. [Default: 1]
- -v, --verbose
Print verbose file-by-file progress messages.
- -q, --quiet
Do not print summary or progress messages.
- --timeout FLOAT
Stop scanning a file if scanning takes longer than a timeout in seconds. [Default: 120]
Force a check and possible reindexing of the cached license index.
Load codebase from an existing JSON scan
- --max-in-memory INTEGER
Maximum number of files and directories scan details kept in memory during a scan. Additional files and directories scan details above this number are cached on-disk rather than in memory. Use 0 to use unlimited memory and disable on-disk caching. Use -1 to use only on-disk caching. [Default: 10000]
- --max-depth INTEGER
Descend at most INTEGER levels of directories including and below the starting point. INTEGER must be positive or zero for no limit. [Default: 0]
All the Core Options are independent options, i.e. They don’t depend on other options.
Please note that different for different install methods, scan commands vary.
The basic command to perform a scan, in case of a download and configure installation (on Linux/MacOS) is:
path/to/scancode [OPTIONS] <OUTPUT FORMAT OPTION(s)> <SCAN INPUT>
The basic usage, if Scancode is installed from
pip, or in Windows:
scancode [OPTIONS] <OUTPUT FORMAT OPTION(s)> <SCAN INPUT>
For more information on how the Scan Command varies for Various Installation Methods/Operating Systems, refer Commands Variation.
Comparing Progress Message Options¶
Default Progress Message:Scanning files for: infos, licenses, copyrights, packages, emails, urls with 1 process(es)... Building license detection index...Done. Scanning files... [####################] 43 Scanning done. Scan statistics: 43 files scanned in 33s. Scan options: infos, licenses, copyrights, packages, emails, urls with 1 process(es). Scanning speed: 1.4 files per sec. Scanning time: 30s. Indexing time: 2s. Saving results.
Progress Message with ``–verbose``:Scanning files for: infos, licenses, copyrights, packages, emails, urls with 1 process(es)... Building license detection index...Done. Scanning files... Scanned: screenshot.png Scanned: README ... Scanned: zlib/dotzlib/ChecksumImpl.cs Scanned: zlib/dotzlib/readme.txt Scanned: zlib/gcc_gvmat64/gvmat64.S Scanned: zlib/ada/zlib.ads Scanned: zlib/infback9/infback9.c Scanned: zlib/infback9/infback9.h Scanned: arch/zlib.tar.gz Scanning done. Scan statistics: 43 files scanned in 29s. Scan options: infos, licenses, copyrights, packages, emails, urls with 1 process(es). Scanning speed: 1.58 files per sec. Scanning time: 27s. Indexing time: 2s. Saving results.
--verboseenables, progress messages for individual files are shown.
With the ``–quiet`` option enabled, nothing is printed on the Command Line.
This option sets scan timeout for each file (and not the entire scan). If some file scan exceeds the specified timeout, that file isn’t scanned anymore and the next file scanning starts. This helps avoiding very large/long files, and saves time.
Also the number (timeout in seconds) to be followed by this option can be a floating point number, i.e. 1.5467.
ScanCode maintains a license index to search for and detect licenses. When Scancode is configured for the first time, a license index is built and used in every scan thereafter.
--reindex-licensesoption rebuilds the license index. Running a scan with this option displays the following message to the terminal in addition to what it normally shows:Checking and rebuilding the license index...
If you want to input scan results from a .json file, and run a scan again on those same files, with some other options/output format, you can do so using the
An example scan command using
--from-json:scancode --from-json sample.json --json-pp sample_2.json --classify
This inputs the scan results from
sample.json, runs the post-scan plugin
--classifyand outputs the results for this scan to
During a scan, as individual files are scanned, the scan details for those files are kept on memory till the scan is completed. Then after the scan is completed, they are written in the specified output format.
Now, if the scan involves a very large number of files, they might not fit in the memory during the scan. For this reason, disk-caching can be used for some/all of the files.
Some important INTEGER values of the
0 - Unlimited Memory, store all the file/directory scan results on memory
-1 - Use only Disk-Caching, store all the file/directory scan results on disk
10000 - Default, store 10,000 file/directory scan results on memory and the rest on disk
An example usage:scancode -clieu --json-pp sample.json samples --max-in-memory -1
Normally, the scan takes place upto the maximum level of nesting of directories possible. But using the
--max-depthoption, you can specify the maximum level of directories to scan, including and below the root location. This can reduce the time taken for the scan when deeper directories are not relevant.
Note that the
--max-depthoption will be ignored if you are scanning from a JSON file using the
--from-jsonoption. In that case, the original depth is used.
An example usage:scancode -clieu --json-pp results.json samples --max-depth 3
This would scan the file