What people actually say about Sourcery
69 mentions across 5 sources · 30% positive · researched Oct 14, 2026
Hacker News, YouTube, Product Hunt, GitHub, Lemmy
What users praise
- • Maintainers close reported bugs fast — PyCharm, spurious-PR-issue, and subscription bugs all fixed within days of report
- • Combines PR review and security scanning (SAST, SCA, secrets, IaC, license) in one gate instead of two vendors
- • One-click suggested fixes, including multi-file resolution, let you commit review changes straight from the PR
What frustrates them
- • Files with PEP 695/PEP 758 syntax are silently skipped and reported as 'No issues detected' — a false all-clear
- • Some reported bugs sit open for over a year with zero maintainer comments (pre-commit EOFError, since Aug 2024)
- • The 'Triplecheck' author groups Sourcery with single-pass bots that 'drop comments' versus a reviewer/coder loop
This is a summary. The full report adds every quote we found, a per-source breakdown, recurring themes, hidden costs and the learning curve — run a free scan below, or see the full Sourcery review.
What comes up again and again about Sourcery
Recurring themes across everything we collected, with where each one showed up.
The 'Sourcery' name collides with Pratchett's Discworld novel, drowning out nearly all real product discussion
mixed · seen on YouTube, Hacker News, Lemmy, Product Hunt
Bot-vs-bot competition: Sourcery is cited alongside CodeRabbit as the single-pass review baseline others try to beat
criticised · seen on Hacker News
Maintainers respond to reported bugs quickly, with same-week closures through Sep–Oct 2026
praised · seen on GitHub
Silent skips on newer Python syntax mean the tool can report a clean PR it never actually reviewed
criticised · seen on GitHub
Editor and platform coverage keeps being requested, and some features stay Enterprise-gated
mixed · seen on GitHub
The Dec 2025 scanner-stack release moved Sourcery into SAST/SCA territory against Semgrep and SonarQube
mixed · seen on Hacker News, GitHub
How hard is Sourcery to learn?
Users describe it as intermediate · typically A few hours to get going
Where people get stuck
- • Configuring custom review rules and custom prompts for the review models
- • Scoping bot token permissions so PR review actions don't create unintended issues
- • Setting up IDE plugins across VS Code, PyCharm, JetBrains, Cursor, and Windsurf
- • Wiring the API to pull findings into your own pipelines
Who Sourcery actually suits
Works well for
- • Python and TypeScript teams on GitHub or GitLab.com whose AI coding agents open PRs faster than humans can read them
- • Small-to-mid engineering orgs wanting review plus security in one gate instead of a review bot plus a separate SAST vendor
- • Developers on VS Code, PyCharm, JetBrains, Cursor, or Windsurf who want issues surfaced before they commit
- • Teams that need an API to pipe security findings into their own pipelines or Jira
Not the right fit for
- • Security teams benchmarking exhaustive taint analysis against Semgrep or SonarQube — Sourcery's own positioning concedes it isn't that
- • Python 3.12+ codebases relying heavily on PEP 695/758 syntax, where files are silently skipped
- • Teams on self-hosted GitHub Enterprise Server without an Enterprise budget
- • Orgs that need thousands of repos under nightly scheduled scan on a mid-tier plan
What people are discussing right now
Discussion volume is low and trending stable
- Comparison against CodeRabbit and single-pass review bots
- Silent skipping of modern Python syntax (PEP 695/758)
- Fast maintainer response on GitHub issues
- Enterprise gating of self-hosting and GHES
- Name collision with Terry Pratchett's Discworld novel
What people really think about Sourcery
A real-time sweep of the open web — social media, forums, review sites, video reviews and live community discussions — distilled into one honest verdict with the actual mentions behind it.
What's inside your Sourcery report
Everything you need to decide — distilled from real, current user opinion.
Live mentions
The actual posts, reviews & complaints about Sourcery — with links and dates.
Honest verdict
A straight answer on whether it lives up to the hype — and who it’s really for.
Praise & gripes
What users genuinely love and the frustrations that keep coming up.
Real quotes
Representative voices from real users, not marketing copy.
Recurring themes
The patterns across hundreds of opinions, surfaced at a glance.
Red flags
Hidden costs and dealbreakers people only discover after signing up.
How it works
Sign up free
Create an account in seconds — get 5 free scans, no card.
We sweep the web
Live social media, forums, reviews & video opinions — in ~30–60s.
Get your report
An honest, downloadable verdict with the real mentions behind it.
Ready to see the real verdict on Sourcery?
Your scan is ready in under a minute · $1.
Top alternatives to Sourcery
Researching options? Explore the closest alternatives.
Diamond by Graphite
Graphite's AI code review agent that comments only on real logic, security, and performance issues in your GitHub pull requests, with one-click fixes.
GitHub Copilot
GitHub Copilot is an AI coding agent that completes code, reviews pull requests, and runs agent tasks from issue to merge.
CodiumAI
Agentic AI code review with a governance layer that enforces your team's coding rules on every pull request
CodeRabbit
AI code review that validates, prioritizes, and secures every pull request your team ships.
Greptile
AI code review agent that checks every pull request against a graph index of your whole codebase
Qodo
Qodo runs agentic AI code review and governance on every pull request, grounded in your codebase, PR history, and tickets.
Check sentiment on these too
Run a live scan on the alternatives before you decide.
Sourcery — questions buyers ask
What do people complain about most with Sourcery?
The complaints that recur most often are files with PEP 695/PEP 758 syntax are silently skipped and reported as 'No issues detected' — a false all-clear, some reported bugs sit open for over a year with zero maintainer comments (pre-commit EOFError, since Aug 2024) and the 'Triplecheck' author groups Sourcery with single-pass bots that 'drop comments' versus a reviewer/coder loop. Drawn from 69 mentions across 5 sources.
What do users like about Sourcery?
Users consistently praise maintainers close reported bugs fast — PyCharm, spurious-PR-issue, and subscription bugs all fixed within days of report, combines PR review and security scanning (SAST, SCA, secrets, IaC, license) in one gate instead of two vendors and one-click suggested fixes, including multi-file resolution, let you commit review changes straight from the PR.
Is Sourcery hard to learn?
Users describe it as intermediate; most people are up and running in a few hours; the usual sticking points are configuring custom review rules and custom prompts for the review models and scoping bot token permissions so PR review actions don't create unintended issues.
Who should not use Sourcery?
Based on what users report, it is a poor fit for security teams benchmarking exhaustive taint analysis against Semgrep or SonarQube — Sourcery's own positioning concedes it isn't that, python 3.12+ codebases relying heavily on PEP 695/758 syntax, where files are silently skipped and teams on self-hosted GitHub Enterprise Server without an Enterprise budget.
What are people saying about Sourcery right now?
Discussion volume is low and trending stable. Current topics: comparison against CodeRabbit and single-pass review bots, silent skipping of modern Python syntax (PEP 695/758) and fast maintainer response on GitHub issues.
How current is this report?
Each scan runs live the moment you click — it reflects what people are saying now, and every report lists the dated mentions behind it.
Can I download it?
Yes — download the full report as a polished, shareable PDF.