surveydown-dev/surveydown

0

/ 100

Documentation77
Engineering53
Health68
R178Other1d ago
Grade a repo

Popular for its size, but the engineering basics lag behind the interest.

Markdown-Based, Programmable Surveys Using R, Quarto, Shiny, and PostgreSQL

Documentation

77

Install and run instructions9pt45

README documents how to install the project.

Contributing guide5pt77

CONTRIBUTING guide found.

README12pt90

README is present.

License6pt100

Licensed under Other.

Engineering

53

Linting and formatting5pt0

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.

Reproducibility6pt0

No dependency lockfile found (−70 pts).

→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.

CI/CD14pt40

CI is configured (.github/workflows/pkgdown.yaml).

Tests18pt80

Test files detected (tests).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

68

Dependency manifest6pt0

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 metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 22
    Forks
  • 3
    Releaseslatest 1y ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 178
    Watchers

Responsiveness

  • 4h
    Median issue response
  • <1h
    Median PR merge time
  • 16
    Open issues
Repository files21 root entries
  • .github
    Good: 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
  • tests
    Good: Test files detected (tests).
  • tools
  • .gitignore
  • .Rbuildignore
  • CLAUDE.md
  • cran-comments.md
  • CRAN-SUBMISSION
  • DESCRIPTION
  • LICENSE
    Good: Licensed under Other.
  • LICENSE.md
  • NAMESPACE
  • NEWS.md
  • README.md
    Good: 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