joinrpg/joinrpg-net
Grade a repo

0

/ 100

GradeD

Getting some notice. Tests and CI would be the fastest wins.

Joinrpg .NET code

Documentation46
Engineering68
Health94
C#20MITtoday

Documentation

46

Install and run instructions9pt0

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

README12pt48

README is present.

Contributing guide5pt61

Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

License6pt100

Licensed under MIT.

Engineering

68

Issue and PR templates6pt0

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.

Reproducibility6pt30

No dependency lockfile found (−70 pts).

→ Enable and commit packages.lock.json so NuGet restores are repeatable.

Tests18pt80

Test files detected (src/JoinRpg.Common.PrimitiveTypes.Test/EmailParseTest.cs).

CI/CD14pt85

CI is configured (.github/workflows/build_and_publish.yml).

Linting and formatting5pt100

.NET formatting configured (.editorconfig).

Project health

94

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt100

Dependency manifest found (docs/Docs.csproj).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • -
    Commits (30d / 90d)
  • 18
    Forks
  • 60
    Releaseslatest 4y ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 20
    Watchers

Responsiveness

  • 59d 19h
    Median issue response
  • <1h
    Median PR merge time
  • 361
    Open issues
Repository files21 root entries
  • .claude
  • .config
  • .github
    Good: CI is configured (.github/workflows/build_and_publish.yml).
    Good: Dependabot covers 2 ecosystems (nuget, github-actions). Dependencies stay current.
  • docs
    Good: Dependency manifest found (docs/Docs.csproj).
  • manifests
    Issue: Build artifacts or local files may be committed (manifests/dev/.env) (−40 pts).Fix: Remove them and add to .gitignore.
  • scripts
  • src
    Good: Test files detected (src/JoinRpg.Common.PrimitiveTypes.Test/EmailParseTest.cs).
  • .editorconfig
    Good: .NET formatting configured (.editorconfig).
  • .git-blame-ignore-revs
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • CLAUDE.md
  • CONTRIBUTING.MD
    Issue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Good: Contributing guide describes the PR/review workflow.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • Directory.Build.props
  • Directory.Packages.props
  • docker-compose.yml
    Good: Environment pinned via docker-compose.yml.
  • global.json
  • Joinrpg.sln.DotSettings
  • Joinrpg.slnx
  • LICENSE.MD
    Good: Licensed under MIT.
  • README.md
    Good: README is present.
    Issue: README is fairly short (−10 pts). At 400+ chars you get partial credit; 1,500+ earns the full +20 pts.Fix: Expand with a description, install steps, usage, and examples.
    Issue: README has some structure (−7 pts). 2-3 headings earns partial credit; 4+ earns the full +15 pts.Fix: Add more sections (Overview, Install, Usage, Contributing) using ## headings.
    Good: README includes screenshots or visuals. Great for first impressions.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    Issue: No live demo link in the README (−20 pts).Fix: Link to a deployed version, docs site, or demo video. Users want to see it running.
    Good: README includes status badges.
    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.