dotnet/windowsdesktop
Grade a repo

61

/ 100

GradeD

Popular for its size, but the engineering basics lag behind the interest.

Higher than 45% of 5,156 graded repos
Documentation59
Engineering53
Health84
Shell210MIT1mo ago

A low grade is a to-do list, not a judgment of your code

Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to C (78).

See your top fixes
Now
D
61
Potential
C
78

Top fixes

Highest-impact changes first, ranked by point weight

23 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 `pull_request:` to the workflow `on:` triggers.

  4. 4
    CI/CD14pt

    Add a lint step to catch style issues automatically.

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

59

Install and run instructions9pt45

README documents how to install the project.

Contributing guide5pt47

CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

README12pt55

README is present.

License6pt100

Licensed under MIT.

Engineering

53

Linting and formatting5pt0

No .NET formatter configured.

→ Add an .editorconfig to define C# formatting rules and run `dotnet format` in CI.

Reproducibility6pt0

No dependency lockfile found (−70 pts).

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

CI/CD14pt40

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

Tests18pt80

Test files detected (src/windowsdesktop/tests).

Issue and PR templates6pt100

Issue or PR templates present.

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 (WindowsDesktop.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)
  • 67
    Forks
  • 164
    Releaseslatest 5y ago

Community

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

Responsiveness

  • 16h
    Median issue response
  • <1h
    Median PR merge time
  • 13
    Open issues
Repository files25 root entries
  • .azuredevops
  • .config
  • .github
    Good: CI is configured (.github/workflows/backport.yml).
    Good: Issue or PR templates present.
  • eng
  • src
    Good: Test files detected (src/windowsdesktop/tests).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • azure-pipelines-PR.yml
  • azure-pipelines.yml
  • build.cmd
  • Build.proj
  • build.sh
  • CODE-OF-CONDUCT.md
  • CODEOWNERS
  • CONTRIBUTING.md
    Issue: CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +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).
    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.
    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
  • Directory.Packages.props
  • es-metadata.yml
  • github-merge-flow.jsonc
  • global.json
  • LICENSE
    Good: Licensed under MIT.
  • NuGet.config
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    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.
    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.
  • WindowsDesktop.sln
    Good: Dependency manifest found (WindowsDesktop.sln).
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/windowsdesktop)](https://www.repo-grade.com/report/dotnet/windowsdesktop)

More graded Shell repos