0
/ 100
Getting some notice. Tests and CI would be the fastest wins.
Documentation
73
Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).
→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.
README documents how to install the project.
README is present.
Licensed under GPL-3.0.
Engineering
46
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.
CI is configured (.github/workflows/test-coverage.yaml).
Test files detected (tests).
Project health
53
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.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 3Forks
- 16Releaseslatest 1y ago
Community
- -Community health
- -authors own >50% of commits
- 10Watchers
Responsiveness
- 28d 8hMedian issue response
- 9d 11hMedian PR merge time
- 6Open issues
Repository files22 root entries
- .githubGood: CI is configured (.github/workflows/test-coverage.yaml).Good: .gitignore present.
- data
- inst
- man
- paper
- R
- src
- testsGood: Test files detected (tests).
- vignettes
- .gitattributes
- .gitignore
- .Rbuildignore
- CLAUDE.md
- cran-comments.md
- DESCRIPTION
- EFAtools.Rproj
- LICENSEGood: Licensed under GPL-3.0.
- NAMESPACE
- NEWS.md
- 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.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.
- README.Rmd
- REWRITE_PLAN.md