Skip to content
testcritic

CodeQL vs Checkmarx One

Feature checklists rarely decide anything. What decides it is the pricing metric, who has to write the tests, and which limitation you can live with.

Entry price

From $30 per active committer/month (GitHub Code Security)

Free tier

Quote on request

Quote only

What drives the bill

The metric that actually scales your invoice.

Free on public repos. For private repositories GitHub split Advanced Security into two products in April 2025: Code Security at $30 and Secret Protection at $19 per active committer/month, both now available on Team plans as well as Enterprise. CodeQL sits in Code Security. Billing counts active committers, not seats, which can surprise teams with many occasional contributors.

Enterprise annual licensing, typically by developer count or lines of code. Six figures at scale.

Free tier

Free for public repositories on GitHub.

Free trial.

Open source

MIT (queries)

Self-hostable

No-code authoring

Languages

JavaScriptTypeScriptPythonJavaC#GoRubySwiftKotlin
JavaC#JavaScriptTypeScriptPythonGoPHPRubyKotlinSwift

Platforms

WebAPIDesktop
WebAPIDesktopMainframe

Fits teams

StartupScale-up / mid-marketEnterprise
Enterprise

Adoption

Widely used

GitHub (Microsoft) · since 2019

Widely used

Checkmarx · since 2006

Strengths

  • Interprocedural dataflow analysis finds real vulnerabilities that regex- and pattern-based tools cannot see.
  • Free on public repositories, with results in the GitHub security tab.
  • Custom queries let you encode organisation-specific security rules.
  • Very deep SAST analysis with wide language coverage including legacy enterprise languages.
  • One platform and one risk view across every scan type.
  • Strong compliance and audit reporting.

Limitations

  • Writing custom CodeQL queries is a specialist skill with a steep learning curve.
  • Analysis is slow — minutes to tens of minutes, so it fits nightly better than per-commit.
  • Private-repo licensing through Advanced Security is expensive at scale.
  • Expensive, with a long procurement and deployment cycle.
  • High false-positive volume typical of deep SAST; tuning is a project.
  • Scans are slow relative to developer-first tools.

Best for

GitHub-hosted projects wanting deep static security analysis, free if the repo is public.

Large enterprises with a security function and regulatory obligations.

All of these integrate with: Jenkins.

Pricing last reviewed August 2026 and is indicative only — confirm on each vendor’s own page.