dotnet/roslyn
Grade a repo

72

/ 100

GradeC

Solid engineering. The biggest lever is setup instructions.

Top 43% of 5,156 graded repos

The Roslyn .NET compiler provides C# and Visual Basic languages with rich code analysis APIs.

Documentation58
Engineering69
Health100
C#20,585MIT7d ago

Top fixes

Highest-impact changes first, ranked by point weight

16 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

58

Install and run instructions9pt0

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

→ Add a section showing how to install dependencies.

Contributing guide5pt72

Contributing guide is detailed and thorough.

README12pt75

README is present.

License6pt100

Licensed under MIT.

Engineering

69

Reproducibility6pt10

No dependency lockfile found (−70 pts).

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

CI/CD14pt57

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

Tests18pt80

Test files detected (eng/config/test).

Linting and formatting5pt100

.NET formatting configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (eng/common/internal/Tools.csproj).

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

  • 225 / 1299
    Commits (30d / 90d)
  • 4,298
    Forks
  • 58
    Releaseslatest 9y ago

Community

  • 87% - Good
    Community health
  • 6 bus factor
    authors own >50% of commits
  • 20,585
    Watchers

Responsiveness

  • 4h
    Median issue response
  • 2h
    Median PR merge time
  • 6,273
    Open issues
Repository files54 root entries
  • .azuredevops
  • .devcontainer
    Good: Environment pinned via .devcontainer/Dockerfile.
  • .github
    Good: CI is configured (.github/workflows/backport.yml).
    Good: Issue or PR templates present.
  • .vscode
  • docs
  • eng
    Good: Test files detected (eng/config/test).
    Good: Dependency manifest found (eng/common/internal/Tools.csproj).
  • scripts
  • src
  • .editorconfig
    Good: .NET formatting configured (.editorconfig).
  • .git-blame-ignore-revs
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .vsconfig
  • AGENTS.md
  • azure-pipelines-compliance.yml
  • azure-pipelines-integration-dartlab.yml
  • azure-pipelines-integration-lsp.yml
  • azure-pipelines-integration-scouting.yml
  • azure-pipelines-integration.yml
  • azure-pipelines-official.yml
  • azure-pipelines-pr-validation.yml
  • azure-pipelines.yml
  • Build.cmd
  • build.sh
  • CODE-OF-CONDUCT.md
  • Compilers.code-workspace
  • Compilers.slnf
  • 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.Packages.props
  • Directory.Solution.props
  • dotnet-tools.json
  • es-metadata.yml
  • global.json
  • Ide.code-workspace
  • Ide.slnf
  • License.txt
    Good: Licensed under MIT.
  • NuGet.config
  • Razor.slnf
  • 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.
    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.
    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.
  • Restore.cmd
  • restore.sh
  • Roslyn.code-workspace
  • Roslyn.lutconfig
  • Roslyn.slnx
  • SECURITY.md
    Good: Security policy present.
  • SpellingExclusions.dic
  • Test.cmd
  • test.sh
  • THIRD-PARTY-NOTICES.txt
  • Verify.cmd
  • verify.sh
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/roslyn)](https://www.repo-grade.com/report/dotnet/roslyn)

More graded C# repos