Know why your GitHub projects get ignored.
Analyze documentation quality, portfolio readiness and repository health in seconds.
Your report appears here. Try any public repository.
README analyzer
Scores clarity, install steps, usage, screenshots and license against what reviewers look for.
Portfolio readiness
Tells you if the repo is ready for recruiters, clients, open source or internships.
Recruiter view
Shows the first impression a hiring manager gets in under a minute.
Best practices
Checks tests, CI, structure, env files and deployment docs.
How it works
- 1
Paste a public repository URL.
- 2
We read the README, file tree and metadata.
- 3
Get scores, gaps and a prioritised fix list.
A sample report
Example data for a fictional repository.
demo/taskflow-app
Repository health
Scores
Checklist
- Clear project description
- Screenshots
- Live demo
- Setup guide
- Architecture
- Clean folder structure
What to fix first
Missing: Screenshots, Live demo, Architecture, Deployment guide, Changelog
What developers say
Placeholder quotes. Replace with real feedback before launch.
I finally understood why my README lost people in ten seconds.
The fix list was specific enough to finish in one evening.
Questions
Does it need access to my code?
No. It reads public repository metadata, the file list and the README through the GitHub API.
Are the scores AI-generated?
Scores come from transparent rules in server/analyzer.js. An AI layer can be added on top for written feedback.
Why did I hit a rate limit?
Unauthenticated GitHub requests are limited. Add a GITHUB_TOKEN to server/.env.