I want to tell you about a problem I kept seeing.
A PR gets opened. It sits there for 2 days. Finally someone glances at it, types "LGTM 👍" and merges it. Three days later production is on fire. There was a SQL injection vulnerability on line 47 that a proper review would have caught in 30 seconds.
This happens everywhere. Every team. Every company. And everyone knows it's happening.
So I built something about it.
What I built
It's called DevPulse. Here's what it does:
Connect your GitHub or GitLab repo, select any PR, and it runs a full AI review in about 30 seconds. Not "consider improving code quality" advice. Actual specific feedback:
- "line 47 — SQL injection vulnerability, here's the snippet, here's how to fix it"
- "you're making a database call inside a loop — this will kill your server under load"
- "this API key is hardcoded — I know you think you'll fix it later, you won't"
Every developer on your team gets a quality score and grade — A+, A, B, C — based on real issues found in their real PRs over time. So you can finally see who's consistently writing clean code and who's been sneaking things past LGTM approvals for months.
Click any developer and get their full profile — commits pulled live from GitHub/GitLab, PR history, what repos they contributed to, what categories of issues they keep introducing, severity breakdown.
There's also a full repo scanner that goes through your entire codebase — not just PRs — and finds vulnerabilities, outdated dependencies, security holes that have been sitting there quietly for months.
The tech stack
- Backend — Python / Django / Django REST Framework
- Frontend — React + Vite, custom design system built from scratch
- AI — Google Gemini API
- Integrations — GitHub API + GitLab API (both fully supported)
What I learned building this solo
Building alone is fast at the start and brutal at the end. The first month I was shipping features every day. By month three I was spending more time context switching between backend, frontend, AI prompts, and API integrations than actually building.
The hardest part wasn't the code. It was making product decisions alone. Every feature, every design choice, every API design — no one to bounce ideas off. You second guess everything.
But it taught me to ship. When you're alone there's no "let me check with the team." You just decide and build.
Why I'm open sourcing it
Because one person can only take something so far.
The product works. The idea is real. The problem is real. What it needs now is more people.
I'm looking for contributors who want to help build this into something real — not just fix bugs but actually shape what this becomes. Backend, frontend, devops, design, AI/ML. If this problem interests you and you want to build something from the ground up, reach out.
And if you're a developer tired of LGTM culture — clone it, run it, break it, tell me what's wrong.
The code:
Backend → https://github.com/Jizhin/devpulse-backend
Frontend → https://github.com/Jizhin/devpulse-frontend
Built this alone. Don't want to keep it that way.
Top comments (0)