See Into Any Repository: Introducing RepoLens
CI scanners and chat-style assistants each cover part of a review. What is often missing is a consistent, audit-friendly pass you can run yourself: security first, then reliability, then architecture—with findings you can act on, not a wall of noise or a conversation that vanishes.
RepoLens is a free, open-source (MIT) command-line tool for that due-diligence layer. Point it at a local project or a remote (GitHub, Bitbucket, Hugging Face, or any Git URL). You bring the model—cloud keys or fully local via Ollama. Nothing has to leave your machine unless you choose a remote provider.
It grew out of the review discipline taught in the CycleRunCode Club: the same P1 → P2 → P3 structure, packaged so anyone can run it on real code.
What is RepoLens?
RepoLens is a structured review CLI, not a hosted SaaS and not a replacement for your test suite or CI scanners. It produces Markdown reports with impact, remediation, and code-example fixes for Critical and High findings. Use it before you ship, when you inherit a repo, or whenever you want a second structured pass alongside tools such as pytest, CodeQL, Dependabot, Semgrep, or Snyk.
Who it is for
- Developers and teams who want a repeatable review format across many repositories
- Mentors and teachers who already use P1 → P2 → P3 when reviewing student or mentee code
- Anyone who prefers BYO model (including local Ollama) over embedding a vendor API key in the tool
Key capabilities
- Full dual review (
repolens review) — P1 security, P2 bugs/reliability/performance, P3 architecture/quality - Security-only guardrail (
repolens sentinel) — P1 playbook without pretending you ran a full architecture audit - Architecture mode (
repolens architecture) — production-readiness focused pass - Bring your own AI — OpenAI, Anthropic, DeepSeek, OpenAI-compatible hosts, or local Ollama
- Graceful LLM handling — invalid model output degrades cleanly and still writes a report
- Deep coverage by default — heuristics plus multi-pass checklist review; gate confidence is not “% secure”
- Optional scanners — OSV-Scanner, Semgrep, and gitleaks can merge into the same report via plugins
- Scan anywhere — local directories or remotes (GitHub, Bitbucket, Hugging Face, generic Git URL)
- Adaptive warm re-reviews — smaller file packs and project-specific timeout hints after the first run
- Opt-in local learning — on-disk only, with informed consent
- GitHub Action — wire into CI when you are ready
Platform and requirements
- Platform: Cross-platform CLI (macOS, Linux, and Windows where Python and tooling allow)
- Runtime: Python 3.11+
- Licence: MIT
- Status: Alpha (
0.1.0a1); Phases 0–5.1 complete — more phases planned - Install today: from GitHub
pip install "repolens @ git+https://github.com/vksvicky/RepoLens.git" - Install next: PyPI (
pip install repolens) after Trusted Publishing setup
Quick start
python3 -m venv .venv
source .venv/bin/activate
pip install "repolens @ git+https://github.com/vksvicky/RepoLens.git"
repolens init --provider ollama
repolens review --path ./my-app --verbose
Remote examples: --github owner/repo, --bitbucket workspace/repo, --hf org/name, or --git-url https://….
Links
- Source: github.com/vksvicky/RepoLens
- Issues: issues/new/choose
- Teaching and shipping feedback: Issue #6
Stars, issues, and pull requests are welcome.