macOS Source beta

See the risk.
Verify the fix.

Follow the evidence.

Review dependency vulnerabilities in local and linked GitHub repositories. See which advisories apply and trace each finding to the dependency that triggered it.

Finding details

Critical

CVE-2021-44906

Detected version
1.2.5
Dependency
minimist
Lockfile
package-lock.json
Explore Review

From lockfile to finding.

  1. Syft

    Builds an inventory of dependencies.

  2. Grype

    Matches packages against known advisories.

  3. CVEC

    Shows the scan evidence behind each finding.

Ask about the 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 Chat
Repository Chatcli-tool

What should I change, and what should I test?

Analysis

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",
GitHub advisory

Give every fix its own workspace.

Create a separate Git worktree for a local finding. Inspect the diff and check results before bringing the change back to your branch.

Worktree diffBranchfix/minimist
package.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 0

Verify the change.

Run a fresh scan after applying the change. Compare the dependency versions and see whether the advisory still matches.

Scan comparisoncli-tool / minimist
Previous scan
1 open finding
Scanned version 1.2.5
After the rescan
0 open findings
Scanned version 1.2.6
View rescan details
Finding
CVE-2021-44906
Rescan outcome
Advisory no longer matches the scanned dependency.
Packages scanned
2 before, 2 after

Local by design.

Scan 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.

Preview chat context

CVEC prepares the context locally. When you send a message, its text and the prepared evidence go to the selected AI connection.

Prompt
What should I change, and what should I test?
Repository
cli-tool Local Git
Selected finding
CVE-2021-44906 Critical
Scan evidence
minimist@1.2.5 in package-lock.json
How CVEC handles your data

Build CVEC for macOS.

Source beta MIT

Building requires access to the private CVEC source repository.

  1. Build from source
  2. Choose a repository
  3. Run your first scan
Source beta setup