Release 2.1.1: Performance and Quality
Performance
Scans are 3 to 5 times faster.
Detection output quality, recall and precision are unchanged.
Measured
| Scenario | Before | After |
|---|---|---|
| 64 source files, 16 workers | 26.3 s | 5.7 s |
| same, default worker count (64) | 29.5 s | 6.7 s |
| 1,500 small files, 16 workers | 11.3 s | 3.4 s |
| 4,000-line shell script | 20.1 s | 1.0 s |
| 8,000-key flat JSON file | 5.3 s | 0.7 s |
| 40,000-line file with 4,000 findings: mapping + SARIF | 24.6 s | 0.2 s |
Bug fixes
- Fixed several problems with
--hashed-values - Addressed a situation when a crashing worker hanged the whole scan.
- Trailing slashes on
--target-dirare now processed correctly - Resolved the #17
- Fix for #21 by @Antiksec
New
--report-diagnosticsadds every file found under the target directory to the SARIF report (run.artifacts, with its status, scan time in milliseconds and, for skipped files, the reason) and per-file errors torun.invocations.
Updates
- The internal JSON report format stays for one more release. It remains deprecated; its removal moves to 2.2.0. Switch to SARIF.