Release Notes - Version 2.0.5

Config scan now skips known non-cryptographic dependency and build directories (such as package caches, version control metadata, and compiler output folders) that can contain tens of thousands of files with no certificate or key material. On a host with VS Code or Teams installed, this alone reduces the number of files inspected by an order of magnitude. Results are also shared across scan phases so the same directory is never traversed more than once per scan run.

Config scan previously processed one application at a time. Multiple applications are now scanned concurrently, so a host running many processes no longer waits for each application to complete before starting the next. Total scan time scales with the slowest individual application rather than the sum of all applications.

The scanner previously made multiple passes over the file list for each application directory — one to locate configuration files and a separate one to locate certificate files. These passes have been merged into a single traversal, halving the file-inspection work per application root. Oversized files are also skipped earlier, before any disk I/O is attempted.

Certificate and key files discovered during the config scan were previously read from disk twice — once to identify the file type and once to extract its contents. Each file is now read once, with the contents passed directly to the extraction step. On endpoints with many bundled certificate files, this reduces disk I/O proportionally to the number of files found.

The config scan and the filesystem certificate scan previously processed the same certificate files independently, performing redundant parsing work. Certificate files handled by the config scan are now tracked and automatically skipped by the filesystem scan, ensuring each file is parsed exactly once per scan run regardless of how many scan phases reference the same application directory.