Semgrep

1.172.0 - 2026-07-28

### Added

• Added support for the OpenTofu .tofu file extension. Because OpenTofu uses the same HCL grammar as Terraform, .tofu files are now automatically detected and scanned as Terraform, so they are picked up by recursive scans and Terraform rulesets (e.g. p/terraform) with no extra configuration. (ENGINE-2884)

### Changed

• Updated the Ruby parser to tree-sitter-ruby v0.23.1, improving support for !=, case/when expressions with line breaks, and element references that take a block. (LANG-206)
• The window for collecting git contributor information during semgrep ci has been extended from the last 30 days to the last 90 days, to match the updated usage policy. (contributor-window-90-days)

### Fixed

• Semgrep will now print richer error messages on segfaults when --debug is NOT passed, matching the segfault error output when --debug is passed (engine-segv)
• Fixed a source of rare, nondeterministic crashes and incorrect results caused

by an OCaml compiler bug. Semgrep now builds against a compiler fork that

backports the upstream fix. (ocaml_codegen_fix)

• Fixed excessive heap growth after explicit major garbage collections. Semgrep

now builds against an OCaml compiler that improves garbage collection duty

cycle pacing. (ocaml_gc_pacing_fix)

• Improved the Scan Status output when no code rules will run (e.g. a

Secrets-only or Supply-Chain-only scan). The summary line no longer reports a

confusing "0 Code rules", and the "Code Rules" section now states explicitly

either that code scanning is not enabled or that there are no code rules to run,

instead of printing an empty table. (ENGINE-2878)

• Fixed lockfileless Gradle dependency resolution failing with "Parsing

dependency output failed (Resolve_gradle.gradle_resolved_dependency)". The

github-dependency-graph-gradle-plugin used during resolution was fetched

unpinned, and its 1.4.2 release renamed keys in its JSON output. The plugin is

now pinned to 1.4.1. (sc-3738)

<br />

<p align="center">

<a href="https://semgrep.dev">

<picture>

<source media="(prefers-color-scheme: light)" srcset="images/semgrep-logo-light.svg">

<source media="(prefers-color-scheme: dark)" srcset="images/semgrep-logo-dark.svg">

<img src="https://raw.githubusercontent.com/semgrep/semgrep/develop/images/semgrep-logo-light.svg" height="100" alt="Semgrep logo"/>

</picture>

</a>

</p>

<h2 align="center">

Code scanning at ludicrous speed.

</h2>

<p align="center">

<a href="https://formulae.brew.sh/formula/semgrep">

<img src="https://img.shields.io/homebrew/v/semgrep?style=flat-square" alt="Homebrew" />

</a>

<a href="https://pypi.org/project/semgrep/">

<img alt="PyPI" src="https://img.shields.io/pypi/v/semgrep?style=flat-square&color=blue">

</a>

<a href="https://semgrep.dev/docs/">

<img src="https://img.shields.io/badge/docs-semgrep.dev-purple?style=flat-square" alt="Documentation" />

</a>

<a href="https://go.semgrep.dev/slack">

<img src="https://img.shields.io/badge/slack-3.5k%20members-green?style=flat-square" alt="Join Semgrep community Slack" />

</a>

<a href="https://github.com/semgrep/semgrep/issues/new/choose">

<img src="https://img.shields.io/badge/issues-welcome-green?style=flat-square" alt="Issues welcome!" />

</a>

<a href="https://github.com/semgrep/semgrep#readme">

<img src="https://img.shields.io/github/stars/semgrep/semgrep?label=GitHub%20Stars&style=flat-square" alt="Star Semgrep on GitHub" />

</a>

<a href="https://hub.docker.com/r/semgrep/semgrep">

<img src="https://img.shields.io/docker/pulls/semgrep/semgrep.svg?style=flat-square" alt="Docker Pulls" />

</a>

<a href="https://hub.docker.com/r/semgrep/semgrep">

<img src="https://img.shields.io/docker/pulls/semgrep/semgrep.svg?style=flat-square" alt="Docker Pulls (Old)" />

</a>

<a href="https://twitter.com/intent/follow?screen_name=semgrep">

<img src="https://img.shields.io/twitter/follow/semgrep?label=Follow%20semgrep&style=social&color=blue" alt="Follow @semgrep on Twitter" />

</a>

</p>

</br>

Semgrep is a fast, open-source, static analysis tool that searches code, finds bugs, and enforces secure guardrails and coding standards. Semgrep supports 30+ languages and can run in an IDE, as a pre-commit check, and as part of CI/CD workflows.

Semgrep is semantic grep for code. While running grep "2" would only match the exact string _2_, Semgrep would match x = 1; y = x + 1 when searching for _2_. Semgrep rules look like the code you already write; no abstract syntax trees, regex wrestling, or painful DSLs.

Note that in security contexts, Semgrep Community Edition will miss many true positives as it can only analyze code within the boundaries of a single function or file. If you want to use Semgrep for security purposes (SAST, SCA, or secrets scanning), the Semgrep AppSec Platform is strongly recommended since it adds the following critical capabilities:

1. Improved core analysis capabilities (cross-file, cross-function, data-flow reachability) that greatly reduce false positives by 25% and increase detected true positives by 250%
2. Contextual post-processing of findings with Semgrep Assistant (AI) to further reduce noise by ~20%. In addition, Assistant enriches findings with tailored, step-by-step remediation guidance that humans find actionable >80% of the time.
3. Customizable policies and seamless integration into developer workflows, giving security teams granular control over where, when, and how different findings are presented to developers (IDE, PR comment, etc.)

The Semgrep AppSec Platform works out-of-the-box with 20000+ proprietary rules across SAST, SCA, and secrets. Pro rules are written and maintained by the Semgrep security research team and are highly accurate, meaning AppSec teams can feel confident bringing findings directly to developers without slowing them down.

Semgrep analyzes code locally on your computer or in your build environment: by default, code is never uploaded. Get started →.

<a href="#option-1-getting-started-from-the-cli">

<img src="https://raw.githubusercontent.com/semgrep/semgrep/develop/images/semgrep-scan-cli.jpg" alt="Semgrep CLI image"/></a>

Language support

Semgrep Code supports 30+ languages, including:

Apex · Bash · C · C++ · C# · Clojure · Dart · Dockerfile · Elixir · HTML · Go · Java · JavaScript · JSX · JSON · Julia · Jsonnet · Kotlin · Lisp · Lua · OCaml · PHP · Python · R · Ruby · Rust · Scala · Scheme · Solidity · Swift · Terraform · TypeScript · TSX · YAML · XML · Generic (ERB, Jinja, etc.)

Semgrep Supply Chain supports 12 languages across 15 package managers, including:

C# (NuGet) · Dart (Pub) · Go (Go modules, go mod) · Java (Gradle, Maven) · Javascript/Typescript (npm, Yarn, Yarn 2, Yarn 3, pnpm) · Kotlin (Gradle, Maven) · PHP (Composer) · Python (pip, pip-tool, Pipenv, Poetry) · Ruby (RubyGems) · Rust (Cargo) · Scala (Maven) · Swift (SwiftPM)

For more information, see Supported languages.

Getting started 🚀

1. From the Semgrep AppSec Platform
2. From the CLI

For new users, we recommend starting with the Semgrep AppSec Platform because it provides a visual interface, a demo project, result triaging and exploration workflows, and makes setup in CI/CD fast. Scans are still local and code isn't uploaded. Alternatively, you can also start with the CLI and navigate the terminal output to run one-off searches.

Option 1: Getting started from the Semgrep Appsec Platform (Recommended)

<a href="https://go.semgrep.dev/login-ghrmgo" target="_blank"><img src="https://raw.githubusercontent.com/semgrep/semgrep/develop/images/semgrep-main-image.jpg" alt="Semgrep platform image"/> </a>

1. Register on <a href="https://go.semgrep.dev/login-ghrmgo" target="_blank">semgrep.dev</a>

1. Explore the demo findings to learn how Semgrep works

1. Scan your project by navigating to Projects > Scan New Project > Run scan in CI

1. Select your version control system and follow the onboarding steps to add your project. After this setup, Semgrep will scan your project after every pull request.

1. [Optional] If you want to run Semgrep locally, follow the steps in the CLI section.

Notes:

If there are any issues, <a href="https://go.semgrep.dev/slack" target="_blank">please ask for help in the Semgrep Slack</a>.

Option 2: Getting started from the CLI

1. Install Semgrep CLI

    # For macOS
    $ brew install semgrep

    # For Ubuntu/WSL/Linux/macOS
    $ python3 -m pip install semgrep

    # To try Semgrep without installation run via Docker
    $ docker run -it -v "${PWD}:/src" semgrep/semgrep semgrep login
    $ docker run -e SEMGREP_APP_TOKEN=<TOKEN> --rm -v "${PWD}:/src" semgrep/semgrep semgrep ci

1. Run semgrep login to create your account and login to Semgrep. This step is optional, but logging into Semgrep gets you access to:

• Semgrep Supply Chain: A dependency scanner that detects reachable vulnerabilities in third party libraries
• Semgrep Code's Pro rules: 600+ high confidence rules written by Semgrep's security research team
• Semgrep Code's Pro engine: An advanced code analysis engine, designed to detect complex vulnerabilities, and reduce false positives

1. Go to your app's root directory and run semgrep ci. This will scan your project to check for vulnerabilities in your source code and its dependencies.

1. Try writing your own query interactively with -e. For example, a check for Python == where the left and right hand sides are the same (potentially a bug):

$ semgrep -e '$X == $X' --lang=py path/to/src

Semgrep Ecosystem

The Semgrep ecosystem includes the following:

• Semgrep Community Edition - The open-source program analysis engine at the heart of everything. Suitable for ad-hoc use cases with a high tolerance for false positives - think consultants, security auditors, or pentesters.

• Semgrep AppSec Platform - Easily orchestrate and scale SAST, SCA, and Secrets scanning across an organization, with no risk of overwhelming developers. Customize which findings developers see, where they see them, and integrate with CI providers like GitHub, GitLab, CircleCI, and more. Includes both free and paid tiers.

• Semgrep Code (SAST) - Make real progress on your vulnerability backlog with SAST that minimizes noise and empowers developers to quickly fix issues on their own, even if they have no security knowledge. Easy to deploy secure guardrails and tailored, step-by-step remediation guidance mean developers actually fix issues since they don't feel slowed down.

• Semgrep Supply Chain (SSC) - A high-signal dependency scanner that detects reachable vulnerabilities in open source third-party libraries and functions.

• Semgrep Secrets (Secrets scanning) - Secrets detection that uses semantic analysis, improved entropy analysis, and validation to accurately surface sensitive credentials in the developer workflow.

• Semgrep Assistant (AI) - Assistant is an AI-powered AppSec engineer that helps both developers and AppSec teams prioritize, triage, and remediate Semgrep findings at scale. Humans agree with Assistant auto-triage decisions 97% of the time, and rate generated remediation guidance as helpful 80% of the time. For an overview of how Assistant works, read this overview.

• Semgrep MCP Server - A Model Context Protocol (MCP) server that lets AI coding assistants run Semgrep scans directly. Integrates with Cursor, VS Code, Windsurf, Claude Desktop, and more. Run semgrep mcp to start it locally.

• Hooks - Automatically trigger Semgrep scans as you code.
• Skills / Prompts - Built-in MCP prompts like write_custom_semgrep_rule help AI assistants write accurate Semgrep rules.
• Claude Code plugin - Available on the official marketplace and via the semgrep/mcp-marketplace repo: /plugin marketplace add semgrep/mcp-marketplace
• Cursor plugin - Available on the official marketplace and via the semgrep/cursor-plugin repo.

Additional resources:

• Semgrep Playground - An online interactive tool for writing and sharing rules.
• Semgrep Registry - 2,000+ community-driven rules covering security, correctness, and dependency vulnerabilities.

Join hundreds of thousands of other developers and security engineers already using Semgrep at companies like GitLab, Dropbox, Slack, Figma, Shopify, HashiCorp, Snowflake, and Trail of Bits.

Semgrep is developed and commercially supported by Semgrep, Inc., a software security company.

Semgrep Rules

Semgrep rules look like the code you already write; no abstract syntax trees, regex wrestling, or painful DSLs. Here's a quick rule for finding Python print() statements.

Run it online in Semgrep’s Playground by clicking here.

<p align="center">

<a href="https://semgrep.dev/playground/r/3qUzQD/ievans.print-to-logger" target="_blank"><img src="https://raw.githubusercontent.com/semgrep/semgrep/develop/images/semgrep-example-rules-editor.jpg" width="582" alt="Semgrep rule example for finding Python print() statements" /></a>

</p>

Examples

Visit Docs > Rule examples for use cases and ideas.

| Use case | Semgrep rule |

| :-------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

| Ban dangerous APIs | Prevent use of exec