0
/ 100
Getting some notice. Tests and CI would be the fastest wins.
My personal dotfiles
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 lift this repo to B (81).
See your top fixesTop fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.
- 2CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3CI/CD14pt
Add a lint step to catch style issues automatically.
- 4CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
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
70
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.
README documents how to install the project.
Licensed under MIT.
Engineering
54
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 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.
CI is configured (.github/workflows/ci.yml).
Lockfile present (mongodb/requirements.txt). Installs are reproducible.
Test files detected (setup/Skills/js-code-analysis/tests).
Project health
100
Dependency manifest found (mongodb/requirements.txt).
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)
- 29Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 71Watchers
Responsiveness
- <1hMedian issue response
- 5hMedian PR merge time
- 4Open issues
Repository files23 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).
- .sisyphus
- config
- custom_nuclei_templates
- docs
- images
- mongodbGood: Lockfile present (mongodb/requirements.txt). Installs are reproducible.Good: Dependency manifest found (mongodb/requirements.txt).
- setupGood: Test files detected (setup/Skills/js-code-analysis/tests).
- tests
- .gitignoreGood: .gitignore present.
- CLAUDE.md
- CONTEXT.md
- DOCKER_FIX.md
- Dockerfile.arch
- Dockerfile.ubuntu
- IMPROVEMENTS.md
- install.sh
- LICENSEGood: Licensed under MIT.
- PROJECT_CONTEXT_GUIDELINE.md
- README_EN.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.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.Good: README documents how to install the project.Good: README documents how to run the project.
- README.md
- test-local.sh
- TESTING.md
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/mswell/dotfiles)