semgrep

Scan source code for security and quality issues with Semgrep.

9|4|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/marduk191/qwen3_mcp --skill semgrep-marduk191
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: semgrep
Source: https://github.com/marduk191/qwen3_mcp/tree/main/skills/static-analysis/skills/semgrep
Command: npx skills add https://github.com/marduk191/qwen3_mcp --skill semgrep-marduk191

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Semgrep provides fast, rule-based static analysis to detect security vulnerabilities and quality issues in source code across languages.

Core Features & Use Cases

  • Pattern-based scanning to catch common vulnerability patterns across languages.
  • Taint mode to track untrusted data flows for more precise detections.
  • Configurable rulesets and custom rules in YAML for CI/CD pipelines.
  • Easy integration with local development and automated security checks.

Quick Start

Install Semgrep and run a quick scan on your codebase to see vulnerabilities and quality issues.

Frequently Asked Questions about semgrep

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

FAQPage Schema
How do I scan source code for security vulnerabilities across multiple languages?

Static analysis scanning detects security vulnerabilities across multiple languages using pattern-matching and taint mode. It identifies bugs and quality issues by applying configurable YAML rules to single files or entire repositories.

How does taint mode improve static analysis for finding bugs?

Taint mode in static analysis improves bug detection by tracking untrusted data flows through your source code. This mechanism enables more precise identification of vulnerabilities where malicious input reaches sensitive functions.

Can I run custom YAML rules for code review in CI/CD pipelines?

You can run custom YAML rules for code review directly in CI/CD pipelines. Configurable rulesets support automated security checks, applying pattern-based scanning to catch common vulnerability patterns during continuous integration workflows.

Do I need Python or Docker to integrate static analysis into local development?

Static analysis integration requires either Python/pip or Docker installation to run. Once installed, you can easily apply these config-driven scans to your local development environment for quick security checks.

What is the best way to configure rulesets for repository-wide code review?

The best way to configure rulesets for repository-wide code review is defining custom rules in YAML. This config-driven approach applies pattern-based scanning across your entire codebase, outputting results in various formats for automated security checks.

Why use pattern-matching instead of other static analysis approaches for security?

Pattern-matching static analysis provides fast, rule-based detection of security vulnerabilities without complex compilation. Unlike heavier approaches, it quickly scans source code across languages using configurable YAML rules to catch common vulnerability patterns.