Getting noticed, but rough fundamentals could turn visitors away.
๐ง My dotfiles on ๏ฃฟ macOS for Neovim, Zsh, Fzf, Ghostty, Kitty, lf, Sketchybar, etc
Documentation
46
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 documents how to install the project.
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
68
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.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- โCommits (30d / 90d)
- 16Forks
- 0Releases
Community
- โCommunity health
- โauthors own >50% of commits
- 234Watchers
Responsiveness
- <1hMedian issue response
- 5hMedian PR merge time
- 0Open issues
Repository files5 root entries
- .config
- .gitignoreGood: .gitignore present.
- .gitignore_global
- .zshenv
- 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.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.Good: README documents how to install the project.Issue: No run or usage instructions found (โ45 pts).Fix: Add a section showing how to start or use the project.