checkmarx-devassist-sca

Scans dependency manifests for vulnerable or malicious open-source packages and remediates findings via Checkmarx MCP.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Open-source dependencies in manifests like package.json, requirements.txt, or go.mod often contain known vulnerabilities or malicious packages that go unnoticed until they cause a breach. This Skill runs a Checkmarx SCA (Software Composition Analysis) scan on dependency files and remediates confirmed findings through the Checkmarx MCP server, so vulnerable packages are identified and fixed without manual CVE research. ## Core Features & Use Cases - On-demand SCA scanning: Runs the Checkmarx cx CLI oss-realtime scan against manifests and lockfiles (package.json, yarn.lock, requirements.txt, go.mod, pom.xml, build.gradle, and more), reporting each package's status, CVEs, severity, and file location. - MCP-driven remediation: Every fix comes from the mcp__Checkmarx__packageRemediation tool — upgrades or removals are applied only to affected dependencies, followed by a re-scan to verify the fix and a structured remediation summary. - Scoped re-scan handling: Distinguishes in-scope findings (packages you changed) from pre-existing ones, preventing version ping-pong loops and uncontrolled edits to unrelated dependencies. - Use Case: A developer asks "are my npm packages safe?" — the Skill scans package.json, flags lodash 4.17.15 with CVE-2020-8203, and on confirmation upgrades it to a fixed version via the Checkmarx MCP, then re-scans to confirm it is clean. ## Quick Start Ask the assistant to scan my package.json for vulnerable dependencies and fix any findings with Checkmarx.

Frequently Asked Questions about checkmarx-devassist-sca

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

FAQPage Schema
How do I scan package.json for vulnerable dependencies?

Run the Checkmarx cx CLI with `cx scan oss-realtime -s package.json` to perform an SCA scan. The output lists each package with its status, CVE identifiers, severity, and file location, and findings can then be remediated through the Checkmarx MCP packageRemediation tool.

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 a single file or several comma-separated files.

What is the difference between SCA scanning and SAST scanning?

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

Can I remediate SCA findings without the Checkmarx MCP server?

No. All remediation must come from the mcp__Checkmarx__packageRemediation tool; manual manifest edits or guessed version bumps are explicitly forbidden. If the MCP is unavailable, validate authentication with `cx auth validate` and restart the session to reconnect it.

Why does the re-scan still show vulnerabilities after remediation?

The scan reads the entire manifest, so it also reports pre-existing findings in packages you did not change — those are out of scope and left untouched. If a package you changed still shows findings after a second remediation attempt, it is reported as unresolved rather than looping through further upgrades.