0
/ 100
Lots of room to improve. Start with a README and CI.
Gulaab sirf phool nahi, ek ehsaas hota hai π Jo bina kahe bhi, dil ki har baat keh jaata hai πΉ 2οΈβ£ Laal gulaab dekar yeh kehna hai humne, tumhari muskaan se hi roshan hai din humare β¨ Rose Day mubarak ho π 3οΈβ£ Har phool khubsurat hota hai, par gulaab ki baat hi alag hai πΉ Bilkul tumhari tarahβ¦ simple, par sabse khaas β€οΈ
A low grade is a to-do list, not a judgment of your code
Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would add 44 points.
See your top fixesTop fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Add automated tests. They prove the code works and give contributors confidence to make changes.
- 2CI/CD14pt
If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.
- 3README12pt
Add an Overview, Install, Usage, and Contributing section at minimum.
- 4README12pt
Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.
Working through the fixes? Let every push regrade itself.
The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
19
README is present.
No install instructions found in the README (β45 pts).
β Add a section showing how to install dependencies.
No CONTRIBUTING.md found (β47 pts base + up to β53 pts more for content).
β Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.
Licensed under GPL-3.0.
Engineering
0
No tests detected anywhere in the repository.
β Add automated tests. They prove the code works and give contributors confidence to make changes.
No CI configuration detected in this repository.
β If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.
No linter or formatter config found.
β Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.
No dependency lockfile found (β70 pts).
β Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
No issue or PR templates found (β100 pts).
β Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.
Project health
47
No dependency manifest detected at root.
β Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.
Repository has a description.
Last pushed 3-6 months ago (β40 pts). A push within 90 days earns 80 pts; within 30 days earns 100 pts.
β A recent commit keeps the project looking alive to visitors and contributors.
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 0Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 0Watchers
Responsiveness
- -Median issue response
- -Median PR merge time
- 0Open issues
Repository files3 root entries
- .gitignoreGood: .gitignore present.
- LICENSEGood: Licensed under GPL-3.0.
- README.mdGood: README is present.Issue: README is very short (β20 pts). 400+ characters earns +10 pts; 1,500+ earns +20 pts.Fix: Add an Overview, Install, Usage, and Contributing section at minimum.Issue: README has little structure (β15 pts). Add 2-3 headings for +8 pts; 4+ earns +15 pts.Fix: Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.Issue: No screenshots or images in the README (β20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.Issue: README has no code examples (β15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.Issue: No live demo link in the README (β20 pts).Fix: Link to a deployed version, docs site, or demo video. Users want to see it running.Issue: No status badges in the README (β10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.Issue: No install instructions found in the README (β45 pts).Fix: Add a section showing how to install dependencies.Issue: No run or usage instructions found (β45 pts).Fix: Add a section showing how to start or use the project.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/nobitanobi9369-a11y/mantasha-rayeen-)