0
/ 100
Fresh project. Add a README and CI early.
Documentation
38
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
No license detected.
→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.
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.
README is present.
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
43
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.
No repository description set on GitHub (−60 pts).
→ Add a one-line description in the repo Settings → About. It appears in search results and social previews.
No .gitignore found (−60 pts).
→ Add a .gitignore to keep build output, node_modules, and secrets out of version control.
Actively maintained (pushed within the last month).
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 0Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 5Watchers
Responsiveness
- -Median issue response
- -Median PR merge time
- 0Open issues
Repository files37 root entries
- about.html
- ads.txt
- apple-touch-icon.svg
- blog-ai-tools.html
- blog-business-card-guide.html
- blog-freelancer-invoice-pakistan.html
- blog-invoice-guide.html
- blog-logo-maker-guide.html
- blog-no-experience-resume.html
- blog-password-guide.html
- blog-qr-guide.html
- blog-resume-tips.html
- blog-scheduler-guide.html
- blog-section.html
- blog-student-tools.html
- blog-upwork-resume-pakistan.html
- business-card-maker.html
- contact.html
- favicon.svg
- INDEX_CHANGES_GUIDE.txt
- index.html
- invoice-generator.html
- logo-maker.html
- logo.svg
- og-image.svg
- password-generator.html
- privacy-policy.html
- qr-code-generator.html
- README.mdGood: README is present.Good: README is well structured with multiple sections.Good: README includes screenshots or visuals. Great for first impressions.Good: README has code examples.Good: README links to a live demo or deployed app.Good: README includes status badges.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.
- resume-builder.html
- robots.txt
- scheduler.html
- script.js
- site.webmanifest
- sitemap.xml
- style.css
- terms.html