83

/ 100

GradeB

Well engineered. The main gaps are CI and a contributing guide.

Top 22% of 5,156 graded repos

Supercharged .NET server side development!

Top fixes

Highest-impact changes first, ranked by point weight

9 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 step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  3. 3
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  4. 4
    CI/CD14pt

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

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

85

Contributing guide5pt25

Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).

→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under MIT.

Engineering

78

CI/CD14pt57

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

Tests18pt80

Test files detected (build/SupervisedTests.cs).

Reproducibility6pt80

Lockfile present (package-lock.json). Installs are reproducible.

Linting and formatting5pt100

.NET formatting configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (package.json).

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)
  • 383
    Forks
  • 277
    Releaseslatest 3y ago

Community

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

Responsiveness

  • 133d 22h
    Median issue response
  • 1d 5h
    Median PR merge time
  • 28
    Open issues
Repository files53 root entries
  • .claude
  • .github
    Good: CI is configured (.github/workflows/tests.yml).
    Good: Issue or PR templates present.
  • .nuke
  • build
    Good: Test files detected (build/SupervisedTests.cs).
  • docker
  • docs
    Good: Security policy present.
  • repro
  • src
  • .editorconfig
    Good: .NET formatting configured (.editorconfig).
  • .gitignore
    Good: .gitignore present.
  • AI-INTEGRATION-RESEARCH.md
  • Analysis.Build.props
  • AZURESERVICEBUS-PERF-DEEP-DIVE-PLAN.md
  • build.cmd
  • build.ps1
  • build.sh
  • CHANGELOG.md
  • ci-improvements.md
  • CLAUDE.md
  • CONNECTION-BUDGET-3397-PLAN.md
  • Directory.Build.props
  • Directory.Build.targets
  • Directory.Packages.props
  • docker-compose.azure-sql-edge.yml
  • docker-compose.yml
    Good: Environment pinned via docker-compose.yml.
  • EXECUTION-PLAN-3376-3397.md
  • GH-3867-BATCHING-PARTITIONING-HANDOFF.md
  • GLOBAL-PARTITIONING-NATIVE-MODE-DESIGN.md
  • GLOBAL-PARTITIONING-ROLLOUT-PLAN.md
  • global.json
  • KAFKA-PERF-DEEP-DIVE-PLAN.md
  • kill-dotnet.bat
  • LICENSE
    Good: Licensed under MIT.
  • mdsnippets.json
  • netlify.toml
  • NEXT-WAVE-HANDOFF.md
  • NEXT-WAVE-RELEASES-PLAN.md
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • PLAN.md
  • pubsub-3258-uncommitted.patch
  • RABBITMQ-PERF-DEEP-DIVE-PLAN.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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • RELEASE-NOTES-DRAFT-MESSAGING-PERF.md
  • RELEASE-PLAN-2026-07-13.md
  • RELEASE-PLAN-2026-07-14.md
  • SQS-PERF-DEEP-DIVE-PLAN.md
  • TRANSPORT-CAPABILITY-RESEARCH-2026-07-18.md
  • wolverine_fsharp.slnx
  • wolverine_slim.slnx
  • wolverine.slnx
  • xunit.runner.json
  • XUNIT3-MIGRATION-PLAN.md
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/jasperfx/wolverine)](https://www.repo-grade.com/report/jasperfx/wolverine)

More graded C# repos