Static analysis · 6 tools
Top 6 open-source code scanning tools for teams avoiding SAST licensing
Semgrep, Opengrep and CodeQL are the first three tools in this shortlist of code scanners for security and bug findings, followed by Bearer, Horusec and PMD. It is written for engineering and AppSec teams that want rule-based static analysis they can run in their own pipelines without buying a commercial SAST license. The order reflects language breadth and rule-authoring flexibility.
| # | Tool | Best for | Key feature | Platforms / deployment | Pricing | More |
|---|---|---|---|---|---|---|
| 1 | SemgrepSemgrep | Teams that want one scanner across CLI, CI and IDE workflows | SAST, SCA and secrets scanning in one platform | CLI, CI/CD, VS Code, JetBrains; PR checks on GitHub, GitLab, Bitbucket, Azure | See vendor pricing page | Introduction |
| 2 | OpengrepOpengrep | Rule authors and teams running SAST in CI on an open license | 30+ languages plus generic matching for templating languages | Release binaries with Cosign signatures; desktop playground; CI mode | See vendor pricing page | Official site |
| 3 | CodeQLGitHub | Security researchers and open source maintainers writing custom queries | Query code as data to find all variants of a vulnerability | CodeQL CLI and Visual Studio Code extension | See vendor pricing page | Introduction |
| 4 | BearerBearer | Teams that also need privacy-focused findings from code | Detects sensitive data flows such as PII and PHI use | Homebrew tap, Docker image (Docker Hub, ghcr.io), prebuilt binaries per OS and architecture | See vendor pricing page | Official site |
| 5 | HorusecZupIT | DevSecOps teams wanting a multi-tool wrapper with a dashboard | Runs multiple security tools across languages at once | CLI, Docker image, VS Code extension, release binaries | See vendor pricing page | Official site |
| 6 | PMDPMD | Java and Apex teams catching common code flaws | More than 400 built-in rules | Command line (check command); Chocolatey on Windows; IDE and CI plugins | See vendor pricing page | Introduction |
1 Semgrep
By Semgrep
Semgrep is an extensible application security platform that scans source code, combining SAST, SCA and secrets scanning. It pairs deterministic static analysis with AI reasoning.
Why it is here: It opens the list because it is the reference point for rule-based code scanning, with registry and custom rules, CLI and CI use, and PR checks across four major Git hosts.
- Best for
- Teams that want one scanner across CLI, CI and IDE workflows
- Key features
- SAST, SCA and secrets scanning in one platform
- CLI, CI/CD and IDE integrations including VS Code and JetBrains
- PR checks on GitHub, GitLab, Bitbucket and Azure
- Triage decisions saved as reusable memories to suppress repeat false positives
- MCP server with a read-only token option for agents
- Limits
- Official pages describe a broader platform than a bare scanning engine. Teams avoiding commercial licensing should check the vendor documentation to confirm which capabilities they need are available in the open-source edition.
- Platforms / deployment
- CLI, CI/CD, VS Code, JetBrains; PR checks on GitHub, GitLab, Bitbucket, Azure
- Pricing
- See vendor pricing page (not quoted here; facts checked 21 November 2026, Asia/Dhaka)
Official website (semgrep.dev) · Read our introduction to Semgrep
2 Opengrep
By Opengrep
Opengrep is an open source SAST engine, forked from Semgrep under the LGPL 2.1 license. It checks source code against rules without executing it.
Why it is here: It sits second because it keeps the Semgrep-style rule approach while documenting 30+ languages, cross-function and cross-file taint analysis, and rules that can carry autofixes.
- Best for
- Rule authors and teams running SAST in CI on an open license
- Key features
- 30+ languages plus generic matching for templating languages
- Taint sources, sinks and sanitizers, with an interfile option for cross-file flows
- CI mode that reports only findings a pull request introduces
- SARIF, JSON, JUnit XML and GitLab output, several at once
- Desktop playground for writing and testing rules
- Limits
- It was created as a fork after Semgrep moved critical features behind a commercial license, so teams should check the vendor documentation for how its rule format and rule sources compare with Semgrep's. Cross-file taint tracking is documented as an option to enable, not a default.
- Platforms / deployment
- Release binaries with Cosign signatures; desktop playground; CI mode
- Pricing
- See vendor pricing page (not quoted here; facts checked 22 November 2026, Asia/Dhaka)
3 CodeQL
By GitHub
CodeQL is GitHub's semantic code analysis engine. It lets you query code as if it were data to find vulnerabilities across a codebase.
Why it is here: It comes third because its query-based model is very flexible for authoring variant-hunting queries and taint tracking, but its documented use terms are narrower than the two tools above.
- Best for
- Security researchers and open source maintainers writing custom queries
- Key features
- Query code as data to find all variants of a vulnerability
- Taint tracking support
- Analysis runs against a CodeQL database, built with the CodeQL CLI or downloaded for open source projects
- Queries run from a Visual Studio Code extension
- Queries can be shared with others
- Limits
- Documented use is restricted to OSI-approved open source codebases, academic research, or specific automated-analysis cases. Other CI/CD use requires contacting sales, so closed-source teams should read the terms first.
- Platforms / deployment
- CodeQL CLI and Visual Studio Code extension
- Pricing
- See vendor pricing page (not quoted here; facts checked 21 November 2026, Asia/Dhaka)
Official website (codeql.github.com) · Read our introduction to CodeQL
4 Bearer
By Bearer
Bearer is a SAST tool that scans source code and analyzes data flows to find and prioritize security and privacy risks. It ships an open source CLI.
Why it is here: It fits fourth because its distinguishing strength is detecting sensitive data flows such as PII and PHI, which is narrower than the general-purpose rule engines above.
- Best for
- Teams that also need privacy-focused findings from code
- Key features
- Detects sensitive data flows such as PII and PHI use
- Privacy report that can feed GDPR compliance reporting
- Findings prioritized by sensitive data flows
- Report lists file location and the lines that triggered each rule
- Extendable by design
- Limits
- The open source CLI is documented as supporting several languages, and advanced cross-file analysis for some languages is part of a separate commercial edition. Check the vendor documentation for your languages.
- Platforms / deployment
- Homebrew tap, Docker image (Docker Hub, ghcr.io), prebuilt binaries per OS and architecture
- Pricing
- See vendor pricing page (not quoted here; facts checked 22 November 2026, Asia/Dhaka)
5 Horusec
By ZupIT
Horusec is an open source static analysis tool from ZupIT that finds security flaws during development. It orchestrates several underlying security tools.
Why it is here: It sits fifth because it covers many languages by running multiple tools at once, which trades the rule-writing flexibility of the engines above for a ready-made bundle and a management dashboard.
- Best for
- DevSecOps teams wanting a multi-tool wrapper with a dashboard
- Key features
- Runs multiple security tools across languages at once
- Searches for key leaks in project files and Git history
- Web application with dashboard, false-positive control and authorization tokens
- Visual Studio Code extension
- Analysis fully configurable through CLI options
- Limits
- Docker is needed to run Horusec with all of its underlying tools. A flag can disable the Docker dependency, at the cost of analysis power. The official pages do not document an in-house rule language.
- Platforms / deployment
- CLI, Docker image, VS Code extension, release binaries
- Pricing
- See vendor pricing page (not quoted here; facts checked 22 November 2026, Asia/Dhaka)
6 PMD
By PMD
PMD is an extensible, cross-language static source code analyzer. It finds common flaws such as unused variables, empty catch blocks and unnecessary object creation.
Why it is here: It closes the list because its documented focus is common programming flaws and code quality rather than security taint analysis, though it offers custom rules in Java or XPath.
- Best for
- Java and Apex teams catching common code flaws
- Key features
- More than 400 built-in rules
- Custom rules written in Java or XPath queries
- Mainly Java and Apex, plus 16 other languages
- CPD copy-paste detector for duplicated code
- IDE and CI plugins, including Eclipse
- Limits
- The documentation describes common programming flaws rather than security-focused data-flow analysis. Scala is supported but no Scala rules are currently available.
- Platforms / deployment
- Command line (check command); Chocolatey on Windows; IDE and CI plugins
- Pricing
- See vendor pricing page (not quoted here; facts checked 21 November 2026, Asia/Dhaka)
Official website (pmd.github.io) · Read our introduction to PMD
How we chose these tools
We looked at three things for each tool: fit with pattern-based scanning for security and bugs, the capabilities its official pages document (rule authoring, taint analysis, language coverage, output formats), and the deployment and platform options it documents (CLI, CI, IDE, containers, binaries). Facts come from official vendor pages, with the date of each check recorded. Anything a vendor does not state, we do not state either.
The order reflects editorial fit for this specific use case: teams that want broad language coverage and room to write their own rules, without a commercial SAST license. It is explained in words in each entry and is not a statement that one tool is better overall. This list is built from documentation rather than product trials, so check the vendor's own docs for your languages, frameworks and licensing terms before you commit.
Order used in this guide: Ordered by language breadth and rule-authoring flexibility among free tools.
Frequently asked questions
What are open-source alternatives to commercial SAST tools?
This shortlist covers Semgrep, Opengrep, CodeQL, Bearer, Horusec and PMD. Opengrep, Bearer's CLI, Horusec and PMD are documented as open source. Semgrep's and CodeQL's official pages do not state their licensing in the facts we checked, and CodeQL documents restrictions on use.
Which tool here supports the most languages?
Opengrep documents support for 30+ languages plus generic matching for templating languages. PMD focuses mainly on Java and Apex and supports 16 other languages. Check each vendor's documentation for your specific languages.
Can I write my own rules?
Yes, in several of them. Opengrep has a desktop playground for writing and testing rules, and PMD accepts custom rules written in Java or XPath. CodeQL lets you write queries and share them, and Semgrep documents custom rules alongside its registry.
Can I use CodeQL on private code in CI?
CodeQL's official pages say use is restricted to OSI-approved open source codebases, academic research, or specific automated-analysis cases. Other CI/CD use requires contacting sales.
Which of these can scan for secrets or sensitive data?
Semgrep documents secrets scanning, and Horusec can search for key leaks in project files and Git history. Bearer detects sensitive data flows such as PII and PHI.
- Semgrep: semgrep.dev, semgrep.dev/about, semgrep.dev/solutions/mcp — checked 21 November 2026
- Opengrep: opengrep.dev, opengrep.dev/about.html — checked 22 November 2026
- CodeQL: codeql.github.com — checked 21 November 2026
- Bearer: github.com/Bearer/bearer, github.com/about, github.com/features — checked 22 November 2026
- Horusec: github.com/ZupIT/horusec, github.com/about, github.com/features — checked 22 November 2026
- PMD: pmd.github.io — checked 21 November 2026
Linthelm is independent and not affiliated with the vendors listed. No vendor paid for inclusion or position. Product names belong to their owners. Features and prices change; confirm details on each official website.