dotnet/orleans
Grade a repo

85

/ 100

GradeB

Well engineered. The main gaps are issue and PR templates and a contributing guide.

Top 22% of 5,156 graded repos

Cloud Native application framework for .NET

Documentation92
Engineering75
Health100
C#10,819MIT6d ago

Top fixes

Highest-impact changes first, ranked by point weight

13 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

92

Contributing guide5pt64

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under MIT.

Engineering

75

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.

Tests18pt80

Test files detected (docs/site/src/content/docs/implementation/snippets/testing/orleans-testing/Sample.OrleansTesting/HelloGrainTests.cs).

CI/CD14pt85

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

Reproducibility6pt92

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

Linting and formatting5pt100

.NET formatting configured (.editorconfig).

Project health

100

Dependency manifest6pt100

Dependency manifest found (docs/site/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)
  • 2,136
    Forks
  • 162
    Releaseslatest 10y ago

Community

  • 62% - Fair
    Community health
  • 4 bus factor
    authors own >50% of commits
  • 10,819
    Watchers

Responsiveness

  • 7h
    Median issue response
  • 1h
    Median PR merge time
  • 739
    Open issues
Repository files38 root entries
  • .azure
  • .azuredevops
  • .config
  • .devcontainer
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Dependabot configured for dotnet-sdk.
  • .vscode
  • assets
  • docs
    Good: Test files detected (docs/site/src/content/docs/implementation/snippets/testing/orleans-testing/Sample.OrleansTesting/HelloGrainTests.cs).
    Good: Lockfile present (docs/site/package-lock.json). Installs are reproducible.
    Good: Dependency manifest found (docs/site/package.json).
  • playground
  • samples
    Good: Environment pinned via samples/Deployment/AzureContainerApps/Clients.MinimalApi/Dockerfile.
  • sign
  • src
  • test
  • .editorconfig
    Good: .NET formatting configured (.editorconfig).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • AGENTS.md
  • aspire.config.json
  • Build.cmd
  • build.ps1
  • CODE-OF-CONDUCT.md
  • common.ps1
  • 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).
    Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Good: Contributing guide includes code examples.
  • Directory.Build.props
  • Directory.Build.targets
  • Directory.Packages.props
  • distributed-tests.yml
  • es-metadata.yml
  • global.json
  • LICENSE
    Good: Licensed under MIT.
  • NuGet.Config
  • Orleans.slnx
  • Parallel-Tests.ps1
  • 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.
  • spelling.dic
  • SUPPORT.md
  • Test.cmd
  • TestAll.cmd
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/orleans)](https://www.repo-grade.com/report/dotnet/orleans)

More graded C# repos