Our take
Activeregular commits and releases- Activity
- 84
- Community
- 90
- Issues
- 52
- Pull requests
- 56
+146 stars in the last 30 days
- Releases more often than 85% of the projects we track
- More contributors than 78% of the projects we track
- Merges more pull requests than 78% of the projects we track
- Slower to close issues than 84% of the projects we track
Opengrep is an actively maintained, broadly contributed SAST engine with a useful migration path for Semgrep rules, though teams should account for LGPL-2.1 obligations and its reported issue-resolution pace.
Good fit if
- You need command-line code analysis across multiple languages and want to write or reuse pattern rules.
- Your team wants an open-source option compatible with existing Semgrep rules, under LGPL-2.1.
- You can use an actively developed tool: commits and releases are recent, contributions come from at least 100 contributors, and contribution activity is not concentrated in one person.
Look elsewhere if
- Your project requires a license other than LGPL-2.1.
- You need a tool that does not depend on custom rules or compatible rule sets to identify the issues you care about.
- Your workflow requires consistently fast issue resolution; reported median issue closure time is about 81 days.
All health signals
| Last commit | 2026-10-05 (1 day ago) |
|---|---|
| Commits, last 90 days | 100+ |
| Releases, last 12 months | 44 (latest v1.30.1, 2026-09-21) |
| Contributors | 100+ (top contributor: 27% of commits) |
| Issues closed, last 90 days | 26 (typically closed in 81 days) |
| Project age | 22 months |
Checked on 2026-10-07 with the GitHub API.
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
3,339Forks
294Change since Nov 14, 2026: +1 stars·0 forks
Overview
Opengrep is a command-line static application security testing (SAST) engine. It searches code for patterns that can indicate security vulnerabilities or other risks, helping developers find problems during development and in CI.
It is a fork of Semgrep and accepts compatible rules, so teams with existing Semgrep rules can use them with Opengrep. Its open-source LGPL-2.1 licensing is intended to keep the engine and its advanced analysis capabilities accessible under an open license.
Key Features
- Scan code with YAML rules that match syntax patterns and report findings.
- Use existing Semgrep-compatible rules and rulesets.
- Analyze code across more than 30 languages, including Python, Java, JavaScript, Go, Rust, PHP, C#, and Visual Basic.
- Trace intrafile taint flows, including field assignments, inter-method flows, higher-order functions, and collection methods.
- Export findings in JSON or SARIF for integration with other tools.
- Install self-contained binaries on Linux, macOS, and Windows.
Use Cases
- Application security teams can run rules against repositories to catch risky code patterns during reviews.
- Developers can write a small custom rule to check for a project-specific coding hazard, such as unchecked
unwrap()calls in Rust. - Teams with Semgrep rules can evaluate an open-source engine option without rewriting those rules.
- CI maintainers can publish scan findings in SARIF for compatible code-scanning workflows.
- Security engineers can investigate taint flows within a file to identify paths from sources to potentially unsafe operations.
What you need
Detected in the repository
- OCaml (main language on GitHub)
- A test suite and automated checks on GitHub Actions
License in plain words
LGPL-2.1weak copyleft
- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the license notice
- Share your changes: yes, changes to the library itself, when you distribute it; linking from closed code is allowed
A summary, not legal advice: the LICENSE file is what applies.
Getting Started
On Linux or macOS, install with:
curl -fsSL https://raw.githubusercontent.com/opengrep/opengrep/main/install.sh | bash
Then scan a repository with rules using opengrep scan -f rules path/to/code. See the README for rule examples, Windows installation, and additional options.
Alternatives
- AgentSec: AgentSec focuses on security risks in AI agent workflows and supported frameworks, rather than general-purpose code scanning with customizable rules.
- hexora: Hexora targets Python threat detection with static rules and machine-learned file scoring, rather than multi-language Semgrep-compatible pattern scanning.
- guardvibe: GuardVibe combines code scanning with checks for dependencies, configuration, and prompts, with rules tailored to modern web stacks.
- wake: Wake is dedicated to Solidity smart contracts and combines static analysis with testing and fuzzing.
| Project | Language | License | Stars | Status |
|---|---|---|---|---|
| opengrep | OCaml | LGPL-2.1 | 3.1k | Active |
| AgentSec | Python | Apache-2.0 | 0 | Active |
| hexora | Rust | MIT | 173 | Active |
| guardvibe | TypeScript | Apache-2.0 | 6 | Active |
| wake | Python | ISC | 376 | Quiet |
Considerations
- The project is a fork of Semgrep, and compatibility with Semgrep rules is a key part of its adoption story. Review the project's documentation for the specific behavior and capabilities you rely on.
- Development is active, with regular commits and releases, and the contributor base is broad rather than concentrated. Issue closure can take time: the measured median is about 81 days.
- The repository is licensed under LGPL-2.1. Review the license and how it applies to your distribution and integration plans.
- The example scan reports only Git-tracked files, so check target selection and scan options when applying it to your own workflow.
Found this useful?
Share it with someone who would like opengrep.