makesurenew

Repository health monitoring dashboard for developer teams. Connect your GitHub repos — get a health score from 0–100, see exactly what's broken, and fix it.

🚀 Live Demo · Report a Bug · Request a Feature

---

What it does

makesurenew scans your GitHub repositories against a set of best practices and gives each one a health score from 0–100. You see at a glance which repos are well-maintained and which need attention — no more manually checking every project.

Check	Points	Why it matters
README.md	30	Onboards contributors and users
GitHub Actions CI	30	Catches regressions automatically
LICENSE file	20	Required for anyone to legally use your code
.gitignore	20	Prevents secrets and binaries from being committed

Score ≥ 80 → Healthy · 50–79 → Needs attention · < 50 → Critical

---

Features

• One-click GitHub OAuth — no new account, no password
• Sync all repos — pulls your full GitHub repository list instantly
• Background scans — health checks run async, no page freezing
• Drill-down view — per-repo breakdown of every passing and failing check
• Actionable hints — each failing check tells you exactly how to fix it
• Dark mode UI — easy on the eyes, mobile-friendly

---

Deploy to Render (free, ~5 min)

5. Trigger a deploy — Render builds the Docker image, copies the frontend, and starts the server.

6. Fork this repo

7. Create a GitHub OAuth App at github.com/settings/developers:

   • Homepage URL: https://makesurenew.onrender.com
   • Callback URL: https://makesurenew.onrender.com/api/auth/callback

8. New → Blueprint on Render → select your fork → it reads render.yaml automatically (web service + PostgreSQL)

9. Set secrets in Render dashboard:

   • GITHUB_CLIENT_ID
   • GITHUB_CLIENT_SECRET

10. Deploy — first build takes ~3 min.

---

Run locally

git clone https://github.com/srj-ai/makesurenew
cd makesurenew
cp .env.example .env
# Fill in GITHUB_CLIENT_ID and GITHUB_CLIENT_SECRET
# GitHub OAuth App callback: http://localhost:8000/api/auth/callback
docker compose up

Open http://localhost:5173 → sign in with GitHub → sync your repos.

---

How scoring works

35 checks run in parallel via GitHub API. Weights sum to 100 — the score is a direct percentage.

Category	Checks	Max pts
Critical	README · CI · Tests · License · CI passing	38
Security	Dependabot · Security policy · Lock file · Type checking	18
Maintainability	Recent commits · Contributing · CODEOWNERS · Linter · Formatter · Docker	17
Discoverability	Releases · Topics · Dev container · Makefile · Good first issues · API docs	12
Polish	Issue templates · PR template · .gitignore · .env.example · pre-commit · SUPPORT · Description · CHANGELOG · Docs · CoC · Stale bot · FUNDING · Homepage · Scorecard	14

• 80–100 — Healthy
• 50–79 — Needs attention
• 0–49 — Critical Open http://localhost:5173

Each failing check includes a direct link to fix it on GitHub.

---

Automation

• Auto-rescan every 6 hours via APScheduler
• Instant rescan on git push via GitHub webhook (POST /api/github/webhook)
• Email alerts when a repo's score drops 10+ points

---

Tech stack

Layer	Technology
Backend	Python 3.12 · FastAPI · PostgreSQL · SQLAlchemy
Frontend	React 18 · TypeScript · Vite · Tailwind CSS
Auth	GitHub OAuth2 · JWT
Automation	APScheduler · GitHub Webhooks
Deploy	Docker · Render.com
Deploy	Docker · Render.com · GitHub Pages (demo)

---

Project structure

makesurenew/
├── backend/
│   └── app/
│       ├── routers/       # auth, repos, dashboard API routes
│       ├── services/      # scanner — GitHub API health checks
│       ├── models.py      # SQLAlchemy ORM models
│       └── main.py        # FastAPI app + static file serving
├── frontend/
│   └── src/
│       ├── api/           # axios client + demo mock data
│       ├── pages/         # Login, Dashboard, RepoDetail
│       ├── components/    # RepoCard, HealthBadge
│       └── hooks/         # useAuth
├── .github/
│   └── workflows/         # CI + GitHub Pages deploy
├── docker-compose.yml     # local development
├── Dockerfile             # production single-service build
└── render.yaml            # Render.com Blueprint config

---

Contributing

PRs are welcome! See CONTRIBUTING.md for setup instructions. Check the open issues — good first issue labels are great starting points. Contributions are welcome! See CONTRIBUTING.md to get started.

• good first issue — great for newcomers
• help wanted — needs more experienced contributors

Please read our Code of Conduct before contributing.

---

Security

Found a vulnerability? Please report it privately — see SECURITY.md.

---

License

MIT © makesurenew contributors