This release makes scan outcomes easier to interpret and more consistent, especially when a scan cannot start or when npm reports only low-severity advisories.
More precise scan outcomes
Preflight now uses a dedicated exit code when it cannot run a scan due to invocation issues, such as an invalid path, unreadable setup, or an unknown check ID. This helps you distinguish “the scan did not run” from “the scan ran and found problems.”
The documented exit codes now include 64 for cases where preflight could not run, while the existing results codes remain the same for successful runs that report warnings or errors.
Fixes and compatibility updates
The vulnerability check now reports npm audit results more accurately when only low-severity advisories are present. Instead of being marked inconclusive with a long report in the message, these cases are treated as a pass and summarized clearly.
Scan output can now be written to a provided destination for both human-readable and JSON formats. This makes it easier to capture and validate output consistently, especially where exact JSON output matters.