dotnet/runtime
Grade a repo

86

/ 100

GradeB

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

Top 20% of 5,156 graded repos

.NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.

Documentation88
Engineering79
Health100
C#18,122MIT5d ago

Top fixes

Highest-impact changes first, ranked by point weight

11 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

88

Contributing guide5pt77

Contributing guide is detailed and thorough.

README12pt85

This repository is large enough that GitHub truncated the file tree. The scan is based on a partial file list, so some checks may under-report.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

79

CI/CD14pt57

CI is configured (.github/workflows/check-no-merge-label.yml).

Tests18pt80

Test files detected (eng/analyzers/PlatformDocAnalyzer.Tests/PlatformDocAnalyzerTests.cs).

Reproducibility6pt92

Lockfile present (.github/workflows/evals/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 (.github/workflows/evals/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

  • 1075 / 3140
    Commits (30d / 90d)
  • 5,533
    Forks
  • 174
    Releaseslatest 5y ago

Community

  • 87% - Good
    Community health
  • 30 bus factor
    authors own >50% of commits
  • 18,122
    Watchers

Responsiveness

  • 2h
    Median issue response
  • 3h
    Median PR merge time
  • 7,678
    Open issues
Repository files38 root entries
  • .azuredevops
  • .claude
  • .config
  • .devcontainer
    Good: Environment pinned via .devcontainer/Dockerfile.
  • .github
    Good: CI is configured (.github/workflows/check-no-merge-label.yml).
    Good: Lockfile present (.github/workflows/evals/package-lock.json). Installs are reproducible.
    Good: Dependabot configured for github-actions.
    Good: Issue or PR templates present.
    Good: Dependency manifest found (.github/workflows/evals/package.json).
    Good: .gitignore present.
  • docs
  • eng
    Good: Test files detected (eng/analyzers/PlatformDocAnalyzer.Tests/PlatformDocAnalyzerTests.cs).
  • src
    Good: Code of conduct present.
  • .clang-format
  • .clang-tidy
  • .CodeQL.yml
  • .dockerignore
  • .editorconfig
    Good: .NET formatting configured (.editorconfig).
  • .git-blame-ignore-revs
  • .gitattributes
  • .gitignore
  • .markdownlint.json
  • .vsconfig
  • build.cmd
  • Build.proj
  • build.sh
  • CODE-OF-CONDUCT.md
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    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.
    Good: Contributing guide includes code examples.
  • Directory.Build.props
  • Directory.Build.rsp
  • Directory.Build.targets
  • Directory.Solution.props
  • dotnet.cmd
  • dotnet.sh
  • es-metadata.yml
  • github-merge-flow.jsonc
  • global.json
  • LICENSE.TXT
    Good: Licensed under MIT.
  • NuGet.config
  • PATENTS.TXT
  • 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.
    Good: README documents how to run the project.
  • SECURITY.md
    Good: Security policy present.
  • THIRD-PARTY-NOTICES.TXT
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/dotnet/runtime)](https://www.repo-grade.com/report/dotnet/runtime)

More graded C# repos