Repository scan
Scan of the cli-tool lockfile.
macOS Source beta
Review dependency vulnerabilities in local and linked GitHub repositories. See which advisories apply and trace each finding to the dependency that triggered it.

Scan of the cli-tool lockfile.
The scanned version falls in the 1.x affected range >=1.0.0 <1.2.6.
Finding details
Critical1.2.5minimistpackage-lock.jsonBuilds an inventory of dependencies.
Matches packages against known advisories.
Shows the scan evidence behind each finding.
Bring the repository scan and advisory into the conversation. Find the change to make and the checks to run for this repository.
Open Repository Chatcli-toolWhat should I change, and what should I test?
Update the direct minimist dependency in package.json to 1.2.6 and refresh package-lock.json.
Run npm test to verify the target and verbose flag and confirm that output paths are preserved as strings. Then rescan to check whether CVE-2021-44906 still matches.
package-lock.json "node_modules/minimist": {
"version": "1.2.5",Create a separate Git worktree for a local finding. Inspect the diff and check results before bringing the change back to your branch.
fix/minimistpackage.json "dependencies": { "minimist": "1.2.5" "minimist": "1.2.6" }}Also changed package-lock.json
npm test2 passed> node --test
✔ reads the target and verbose flag
✔ keeps output paths as strings
ℹ pass 2
ℹ fail 0Run a fresh scan after applying the change. Compare the dependency versions and see whether the advisory still matches.
cli-tool / minimist1.2.51.2.6CVE-2021-44906Scan results and history live on your Mac. Scanning and review work without an AI connection. If you use Repository Chat, you can review the context before sending it to your chosen provider.
CVEC prepares the context locally. When you send a message, its text and the prepared evidence go to the selected AI connection.
CVE-2021-44906 Criticalminimist@1.2.5 in package-lock.jsonSource beta MIT
Building requires access to the private CVEC source repository.