deepsec vs pr-lens
deepsec is much bigger: 8.2k stars against 2.1k. Over the days we have tracked them deepsec moved +33.4% and pr-lens +186.6%, so pr-lens is growing faster right now.
They split the axes: deepsec leads on context depth and customization, pr-lens on model freedom and setup ease.
Stars and commit dates come from our own daily tracking. The six axes are read off each project's documentation by our review pipeline, so they describe what a project says about itself, not what we measured in its code.
Where they stand today
Agent-powered whole-repo vulnerability scanner that scales across workers, resumes interrupted runs, and lets you grow project-specific matchers.
- Stars
- 8.2k
- Tracked growth
- +33.4%
- Maturity
- ●●●●●
- Last commit
- 21d ago
- Language
- TypeScript
- License
- Apache-2.0
- Cost to run
- Uses your model API keys; full-repo scans can be costly for large repos
Generates animated architecture and data-flow diagrams that visualize a PR’s blast radius and step-by-step walkthroughs directly inside the pull request.
- Stars
- 2.1k
- Tracked growth
- +186.6%
- Maturity
- ●●●●●
- Last commit
- 2d ago
- Language
- TypeScript
- License
- MIT
- Cost to run
- Free for open source; otherwise your API key
Six axes, head to head
Each axis runs 0 to 5. The label under a score is what that project's own docs claim, not a category average.
| Axis | deepsec | pr-lens |
|---|---|---|
Context depth How much of your codebase it sees before it answers: the open diff, the diff plus related files, or the whole repository. | ●●●●● Whole-repo analysis | ●●●●● Diff + related files |
Noise control How it keeps output volume down — severity thresholds, deduplication, incremental runs over new commits only. | ●●●●● Revalidate + matchers | ●●●●● Configurable filters |
Customization How far it bends to your team: custom rules, prompts, style guides, per-path config. | ●●●●● Plugins & matchers | ●●●●● Config file options |
Privacy Whether your code stays on your own infrastructure: fully local, self-hostable, or cloud API only. | ●●●●● Cloud APIs with key | ●●●●● Cloud API key |
Model freedom Whether you can point it at any provider, or it is wired to one. | ●●●●● BYOK & providers | ●●●●● Bring-your-own key |
Setup ease What it takes to get a first useful run out of it. | ●●●●● Config + API key | ●●●●● One-click App |
Which one to pick
Pick deepsec if…
High-coverage — pick deepsec when you need an agent-driven, tunable scanner that analyzes entire large codebases and supports custom matchers and distributed execution.
- Context depth: Whole-repo analysis (5/5 against 3/5)
- Customization: Plugins & matchers (5/5 against 3/5)
Pick pr-lens if…
Visual-first — install the GitHub App to get animated architecture and data-flow diagrams posted automatically to every PR so you can understand a change before reading its code.
- Model freedom: Bring-your-own key (5/5 against 3/5)
- Setup ease: One-click App (5/5 against 3/5)
What people want from each one
vercel-labs/deepsec
coldteadotai/pr-lens
Questions people ask
Is deepsec better than pr-lens?
They split the axes: deepsec leads on context depth and customization, pr-lens on model freedom and setup ease. deepsec is worth picking when high-coverage — pick deepsec when you need an agent-driven, tunable scanner that analyzes entire large codebases and supports custom matchers and distributed execution.
Which of deepsec and pr-lens keeps my code private?
deepsec: Cloud APIs with key (3/5). pr-lens: Cloud API key (3/5).
What does each one cost to run?
deepsec: Uses your model API keys; full-repo scans can be costly for large repos. pr-lens: Free for open source; otherwise your API key.
Full profiles: vercel-labs/deepsec and coldteadotai/pr-lens. Everything else in Code review agents.