cx-devassist-sca

Scans dependency manifests with Checkmarx SCA and remediates vulnerable packages via MCP.

2|Updated Jun 10, 2026
One-click install
npx skills add https://github.com/Checkmarx/cx-agentic-ai --skill cx-devassist-sca-checkmarx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cx-devassist-sca
Source: https://github.com/Checkmarx/cx-agentic-ai/tree/main/plugins/cursor-devassist/skills/cx-devassist-sca
Command: npx skills add https://github.com/Checkmarx/cx-agentic-ai --skill cx-devassist-sca-checkmarx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Open-source dependencies in manifests like package.json, requirements.txt, go.mod, and pom.xml often contain known vulnerabilities or malicious packages that go unnoticed until they are exploited. This Skill runs a Checkmarx SCA (Software Composition Analysis) scan on dependency manifests and lockfiles, reports vulnerable or malicious packages, and remediates them through the Checkmarx MCP server. ## Core Features & Use Cases - On-demand SCA scanning: Run cx scan oss-realtime against manifests and lockfiles (package.json, yarn.lock, requirements.txt, go.mod, pom.xml, build.gradle, and more) and interpret each package's status (OK, Unknown, Malicious, Vulnerable) with CVE, severity, and location details. - MCP-driven remediation: Every fix comes from the Checkmarx packageRemediation MCP tool, which supplies fixed versions or alternative packages; manual edits, guessed version bumps, and web/registry searches are explicitly forbidden. - Scoped re-scan and suppression: After fixing, the Skill re-scans, remediates only findings tied to changed packages, and suppresses unfixable findings via cx ignore-vulnerability with a structured summary. - Use Case: A developer asks "are my npm packages safe?" The Skill scans package.json, finds a vulnerable lodash version with CVE-2020-8203, obtains the fixed version from the Checkmarx MCP, upgrades only that dependency, and confirms it is clean on re-scan. ## Quick Start Ask the assistant to scan your dependency manifest, for example: "Scan my package.json for vulnerable dependencies and fix any findings."

Frequently Asked Questions about cx-devassist-sca

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scan my dependencies for vulnerabilities with Checkmarx?

Run the Checkmarx cx CLI with `cx scan oss-realtime -s <manifest-path>` against a manifest or lockfile such as package.json or requirements.txt. The scan returns JSON listing each package's status, CVEs, severities, and file locations.

How do I fix vulnerable npm or pip packages found by an SCA scan?

Fixes come exclusively from the Checkmarx MCP packageRemediation tool, which returns remediation steps such as a fixed version or an alternative package. Manual manifest edits, guessed version bumps, and registry searches are not permitted.

Which manifest and lockfile formats does Checkmarx SCA scanning support?

Supported files include package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, requirements.txt, Pipfile.lock, go.mod, go.sum, pom.xml, build.gradle, and build.sbt. The `-s` flag accepts one file or several comma-separated files.

What is the difference between SCA scanning and SAST scanning?

SCA scans dependency manifests and lockfiles for vulnerable or malicious open-source packages, while SAST scans source code files like .py, .js, or .java for code-level vulnerabilities. Use the cx-devassist-asca skill for source code and this skill for dependencies.

What happens if the Checkmarx MCP remediation tool is not available?

Remediation stops entirely and no dependency is modified, since all fixes must come from the MCP tool. The Skill verifies cx authentication with `cx auth validate` and asks the user to reload the window so the MCP server reconnects.

What if a vulnerable package has no fixed version available?

If the packageRemediation response offers no fixed version and no alternative package, the finding is suppressed using `cx ignore-vulnerability --scan-type sca` with a JSON payload. The suppressed package is recorded in the remediation summary rather than treated as a TODO.