punishxiv/questionable
Grade a repo

71

/ 100

GradeC

Solid engineering. The biggest lever is issue and PR templates.

Top 39% of 5,156 graded repos
Documentation73
Engineering72
Health84
C#24AGPL-3.02d ago

Top fixes

Highest-impact changes first, ranked by point weight

18 to address
  1. 1
    Tests18pt

    Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.

  2. 2
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  3. 3
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

  4. 4
    CI/CD14pt

    Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.

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.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

73

Install and run instructions9pt45

README documents how to install the project.

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.

README12pt85

README is present.

License6pt100

Licensed under AGPL-3.0.

Engineering

72

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.

Reproducibility6pt70

Lockfile present (GatheringPathRenderer/packages.lock.json). Installs are reproducible.

Tests18pt80

Test files detected (QuestPathGenerator.Tests/QuestGeneratorTest.cs).

CI/CD14pt85

CI is configured (.github/workflows/pr-test.yml).

Linting and formatting5pt100

.NET formatting configured (.editorconfig).

Project health

84

Repository metadata5pt40

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.

Dependency manifest6pt100

Dependency manifest found (Questionable.sln).

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)
  • 60
    Forks
  • 680
    Releaseslatest 11mo ago

Community

  • 50% - Fair
    Community health
  • 1 bus factorlow
    author own >50% of commits
  • 24
    Watchers

Responsiveness

  • 10h
    Median issue response
  • <1h
    Median PR merge time
  • 23
    Open issues
Repository files28 root entries
  • .github
    Good: CI is configured (.github/workflows/pr-test.yml).
  • .vscode
  • GatheringPathRenderer
    Good: Lockfile present (GatheringPathRenderer/packages.lock.json). Installs are reproducible.
  • GatheringPaths
  • Questionable
  • Questionable.IpcTest
  • Questionable.Model
  • Questionable.Tests
  • QuestPathGenerator
  • QuestPathGenerator.Tests
    Good: Test files detected (QuestPathGenerator.Tests/QuestGeneratorTest.cs).
  • QuestPaths
  • QuestPaths.JsonValidator
  • .editorconfig
    Good: .NET formatting configured (.editorconfig).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • AGENTS.md
  • CHANGELOG.md
  • CODEOWNERS
  • 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.Build.targets
  • global.json
  • LICENSE
    Good: Licensed under AGPL-3.0.
  • nuget.config
  • Questionable.sln
    Good: Dependency manifest found (Questionable.sln).
  • Questionable.sln.DotSettings
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    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.
    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.
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/punishxiv/questionable)](https://www.repo-grade.com/report/punishxiv/questionable)

More graded C# repos