SAST + Code Review Automation

Every PR reviewed.
Every risk flagged.

Gritcadence runs static analysis on every pull request and surfaces findings as inline PR comments — CWE-mapped, severity-graded, on the exact line. No separate dashboard. No per-seat pricing.

Works where your team already reviews code.
views.py — pull/142 48 def get_user_data(request): 49 user_id = request.GET.get('id') 50 conn = get_db_connection() 51 cursor.execute( f"SELECT * FROM users WHERE id={user_id}" ) GRCD-0081 HIGH SQL injection risk · cursor.execute() with f-string Use parameterized queries: cursor.execute("… WHERE id=%s", (user_id,)) 52 result = cursor.fetchone() 53 return JsonResponse(result) 55 + cursor.execute( "SELECT * FROM users WHERE id=%s", (user_id,) ) 55 - cursor.execute(f"SELECT * FROM users WHERE id={user_id}") gritcadence-bot 1 finding GRCD-0081: SQL injection via unsanitized query parameter (CWE-89) Confidence: HIGH · Language: Python · Rule: sql-injection/cursor-fstring
85%

of vulnerabilities are introduced during development, not discovered in production. The fix window is the pull request — not the post-mortem.

cost increase to remediate a vulnerability after merge versus catching it at review time. Taint analysis in CI catches it before context is lost.

40+

pull requests per week for a typical 5-person team. Running 500+ SAST rules automatically on changed code is the only way to keep up at that rate.

How it works

Review automation in three steps

Connect once. Security coverage on every PR from that point forward.

01

Connect your repo

Install the GitHub App in under 2 minutes. Select which repos to scan. No code changes, no CI pipeline edits required.

02

Rules run on every PR

500+ built-in SAST rules covering OWASP Top 10 and CWE. Plus your custom YAML rules. Scans start automatically on push.

03

Findings appear inline

Security findings show up as inline PR review comments — exactly where your team is already looking. No context switch to a separate dashboard.

Features

Built for the review workflow, not a compliance report

Findings appear on the line, in the PR, at review time. Not in a separate tool you open three days later.

SAST Engine

500+ rules. OWASP Top 10. CWE mapping.

Built-in rules cover the vulnerabilities that matter: SQL injection, XSS, insecure deserialization, hardcoded credentials, path traversal. Mapped to OWASP Top 10 and CWE IDs for traceability.

  • Python, JavaScript/TypeScript, Go, Java, Ruby, Rust
  • CWE IDs in every finding for bug-tracker integration
  • Confidence scoring reduces noise at the source
scan results · PR #142
51 HIGH GRCD-0081 sql-injection
CWE-89 cursor.execute() with f-string — use parameterized queries
23 MED GRCD-0204 xss-unsanitized-output
88 LOW GRCD-0317 missing-auth-check
3 findings · 2 files scanned · 0.8s
PR Automation

Findings inside the PR, not in another tab

Gritcadence posts findings as inline review comments on the exact lines where issues were detected. Reviewers see them in context — no dashboard login, no separate tool.

  • Inline comment with rule ID, severity, and fix suggestion
  • PR blocked from merge on HIGH severity (configurable)
  • Re-scan on every push automatically
gritcadence-bot comment
▸ views.py line 51
GRCD-0081 · SQL injection risk (CWE-89)
Confidence: HIGH · Pattern: cursor-fstring
Suggestion: use parameterized queries
cursor.execute("SELECT … WHERE id=%s", (user_id,))
Custom Rules

Extend with YAML rules your team writes

Your codebase has patterns no off-the-shelf scanner knows about. Gritcadence's rule DSL lets you write detection logic in YAML — no AST expertise required.

  • Pattern matching with taint tracking support
  • Test harness to validate rules before deploying
  • Shared rule library across repos in a team
rules/custom/no-raw-sql.yaml
1id: GRCD-CUSTOM-001
2severity: high
3language: python
4pattern: |
5 cursor.execute(f"...")
6message: Use parameterized queries
Integrations

Works where your team reviews code

Native PR comments. No context switch.

GitHub
GitLab
Bitbucket
GitHub Actions
Slack
Jira
Linear
Azure DevOps
Early adopters

What engineering teams say

"We had a SQLi sitting in prod for over a year — it passed review because the data flow wasn't obvious from the diff. Gritcadence flags it at the line with the taint path in the comment. That's the gap it closes."

Staff Engineer
Fintech payments platform

"We'd tried two SAST tools before this. Both got turned off after a month — the false positive rate was high enough that engineers stopped reading the output. Gritcadence's confidence scoring and suppression workflow kept the signal actionable."

Security Lead
Cloud infrastructure company
Pricing

Simple, per-team pricing

No per-seat surprises. Priced per team by repository pool.

Starter
$0 /month

Up to 3 repositories

  • 500+ built-in rules
  • GitHub + GitLab
  • Community + docs
  • Custom rules
  • API access
Pro
$79 /month

Up to 25 repositories · 14-day free trial

  • Everything in Starter
  • Custom YAML rules
  • API access
  • Email support, <1 business day
  • SSO
Team
$249 /month

Unlimited repos · 14-day free trial

  • Everything in Pro
  • Shared rule library
  • SSO (SAML/OIDC)
  • Priority support + Slack
  • Team dashboards

Security coverage without the context switch.

Start with Starter — free, no credit card, 3 repos, 500+ built-in rules. Upgrade when your repo count grows.

Or reach us at [email protected]