Some interest. A stronger README and CI would help.
A Better Rolls port for SWADE
Documentation
39
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.
README is present.
Licensed under GPL-3.0.
Engineering
30
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
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/main.yml).
Lockfile present (package-lock.json). Installs are reproducible.
Linter or formatter configured (eslint.config.js).
Project health
86
Dependency manifest found (package.json).
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
- 27Releaseslatest 11d ago
Community
- —Community health
- —authors own >50% of commits
- 16Watchers
Responsiveness
- 19hMedian issue response
- 1hMedian PR merge time
- 0Open issues
Repository files17 root entries
- .githubGood: CI is configured (.github/workflows/main.yml).
- assets
- config
- css
- docs
- lang
- scripts
- templates
- .gitignoreGood: .gitignore present.
- CHANGELOG.md
- codebook.toml
- eslint.config.jsGood: Linter or formatter configured (eslint.config.js).
- LICENSEGood: Licensed under GPL-3.0.
- module.json
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- package.jsonGood: Dependency manifest found (package.json).
- README.mdGood: README is present.Good: README is well structured with multiple sections.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.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.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.