0
/ 100
Popular for its size, but the engineering basics lag behind the interest.
Markdown-Based, Programmable Surveys Using R, Quarto, Shiny, and PostgreSQL
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 C (77).
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 `pull_request:` to the workflow `on:` triggers.
- 4CI/CD14pt
Add a lint step to catch style issues automatically.
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
77
README documents how to install the project.
CONTRIBUTING guide found.
README is present.
Licensed under Other.
Engineering
53
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.
CI is configured (.github/workflows/pkgdown.yaml).
Test files detected (tests).
Issue or PR templates present.
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)
- 22Forks
- 3Releaseslatest 1y ago
Community
- -Community health
- -authors own >50% of commits
- 178Watchers
Responsiveness
- 4hMedian issue response
- <1hMedian PR merge time
- 16Open issues
Repository files21 root entries
- .githubGood: CONTRIBUTING guide found.Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.Good: Code of conduct present.Good: CI is configured (.github/workflows/pkgdown.yaml).Good: Issue or PR templates present.Good: .gitignore present.
- inst
- man
- pkgdown
- R
- testsGood: Test files detected (tests).
- tools
- .gitignore
- .Rbuildignore
- CLAUDE.md
- cran-comments.md
- CRAN-SUBMISSION
- DESCRIPTION
- LICENSEGood: Licensed under Other.
- LICENSE.md
- 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.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.
- README.Rmd
- surveydown.Rproj
- todo.md
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/surveydown-dev/surveydown)