0
/ 100
Popular for its size, but the engineering basics lag behind the interest.
Pipe-friendly Framework for Basic Statistical Tests in R
Documentation
63
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
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/R-CMD-check.yaml).
Test files detected (tests).
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)
- 57Forks
- 13Releaseslatest 5y ago
Community
- -Community health
- -authors own >50% of commits
- 488Watchers
Responsiveness
- 12hMedian issue response
- <1hMedian PR merge time
- 53Open issues
Repository files19 root entries
- .githubGood: CI is configured (.github/workflows/R-CMD-check.yaml).Good: .gitignore present.
- docs
- inst
- man
- pkgdown
- R
- testsGood: Test files detected (tests).
- tools
- _pkgdown.yml
- .gitattributes
- .gitignore
- .Rbuildignore
- cran-comments.md
- DESCRIPTION
- 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.Good: README documents how to run the project.
- README.Rmd
- rstatix.Rproj