Skip to content
Semgrep logo

Semgrep

Static analysis and AppSec platform where rules are readable code patterns, plus a plugin that scans every file an AI coding agent writes.

4.5/5 my assessment
Freemium
Software

Overview

The core of Semgrep is an open source static analysis engine that has been on GitHub for years and supports more than 30 languages. What sets it apart is the rule syntax. A rule is a pattern that resembles the source it matches, so writing one does not require picking up a separate query language the way CodeQL does. For an engineering lead this matters more than any feature list. House rules that encode your own past incidents are the checks that actually prevent repeats, and Semgrep is the tool where writing them takes an hour rather than a sprint.

The commercial platform adds cross-file and cross-function analysis, Supply Chain and Secrets, plus the AI layer renamed Multimodal on 19 March 2026. Autofix reached public beta three days earlier, generating draft pull requests with line-level breaking change analysis instead of blind patches. The more interesting release is Guardian, which installs into AI coding agents directly and scans what they produce as they produce it, using the same Code, Supply Chain and Secrets engines. Semgrep was also selected for OpenAI's Trusted Access for Cyber Program, which buys it early access to models with stronger security reasoning. Whether that turns into measurably better detection is worth watching rather than assuming.

The honest limits are about scale and language. Interfile analysis defaults back to single-file mode past 5 GB of memory or a three hour scan, and Ruby, PHP, Swift and Rust get no cross-file coverage at all. Teams on those stacks should test against their actual repository before signing anything. Everyone else, especially a team of ten or fewer that fits inside the free tier, should run it before paying for something more expensive. The gap between what Semgrep gives away and what most vendors charge for is the strongest argument in its favour.

Key Features

  • Rules written as patterns that look like the code they match, so a team can ship a house rule in an afternoon without learning a separate query language
  • Cross-file and cross-function taint analysis for C#, Go, Java, JavaScript, Kotlin, Python, TypeScript and C/C++
  • Semgrep Multimodal, the March 2026 rename of Assistant, combines static analysis with model reasoning to surface IDOR and broken authorization
  • Autofix, in public beta since 16 March 2026, opens draft pull requests with line-level breaking change analysis for Code and Supply Chain findings
  • Semgrep Guardian installs into AI coding agents as an MCP server with hooks and skills, scanning each file the agent touches
  • Code, Supply Chain and Secrets in one platform, with rule-level policy scoping across projects, tags and exceptions

Where it holds

  • Rule authoring is the best in the category. A security engineer can write and ship a custom check the same day they think of it
  • Signal quality. Reviewers repeatedly cite low false positive rates, which is the difference between a scanner developers use and one they mute in week two
  • The free tier is unusually generous at 10 contributors and 10 private repos with the real platform, not a crippled demo
  • Guardian puts enforcement at the moment AI-written code is produced instead of after it lands in main

Where it breaks

  • Cross-file analysis does not cover Ruby, PHP, Swift or Rust, which quietly rules out a lot of real codebases
  • Interfile scans fall back to single-file mode past 5 GB of memory or three hours of runtime, and there are open reports of taint results vanishing on repositories over a thousand files
  • AI credits are metered per developer per month, so heavy Autofix use hits the Teams ceiling of 20 credits quickly

My Take

Against Snyk on static analysis this is not close. Semgrep finds more with less noise and the reason is structural: a rule is a pattern that resembles the source it matches, so an engineer who can read Python can encode the specific mistake their team keeps repeating. Guardian, the plugin that drops an MCP server plus hooks into Cursor or Claude Code and scans every file the agent writes, is the most sensible thing any AppSec vendor has shipped for agent workflows so far. The caveat is coverage. Cross-file taint analysis skips Ruby, PHP, Swift and Rust entirely, and interfile scans drop to single-file mode above 5 GB of memory, so a large monorepo can be getting shallower analysis than the dashboard suggests.

Francis Okafor
Francis Okafor AI & Tech Lead · Engineer

Quick Info

Pricing:
freemium
Openness:
Open source
Licence:
LGPL-2.1 (OSS engine)
Starting at:
Free Edition covers up to 10 contributors and 10 private repositories at no cost with the full platform. Teams starts at $30 per contributor per month, caps at 500 private repositories and includes 20 AI credits per developer per month. Enterprise is custom quoted, raises that to 50 AI credits per developer per month and adds SSO, on-prem support, custom CI/CD integrations and a custom AI model provider option. The command line engine stays open source and free.
Added:
Aug 2026
Updated:
Aug 2026

Use Cases

software development automation agent development

Judge it on your own work

The notes above say where Semgrep holds and where it breaks. The fastest check is your own workload.

Visit website ↗

Alternatives to Semgrep