microsoft/wsl
Grade a repo

84

/ 100

GradeB

A top-tier open source project. Docs, tests, and CI are all in excellent shape.

Top 20% of 5,156 graded repos

Windows Subsystem for Linux

Documentation90
Engineering78
Health100
C++32,817MIT1mo 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

90

Contributing guide5pt77

Contributing guide is detailed and thorough.

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

78

CI/CD14pt57

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

Tests18pt80

Test files detected (test).

Reproducibility6pt80

Lockfile present (distributions/requirements.txt). Installs are reproducible.

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (distributions/requirements.txt).

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

  • 127 / 365
    Commits (30d / 90d)
  • 1,759
    Forks
  • 103
    Releaseslatest 4y ago

Community

  • 100% - Good
    Community health
  • -
    authors own >50% of commits
  • 32,817
    Watchers

Responsiveness

  • 1h
    Median issue response
  • 16h
    Median PR merge time
  • 925
    Open issues
Repository files39 root entries
  • .config
  • .github
    Good: CI is configured (.github/workflows/distributions.yml).
    Good: Issue or PR templates present.
  • .pipelines
  • cloudtest
  • cmake
  • diagnostics
  • distributions
    Good: Lockfile present (distributions/requirements.txt). Installs are reproducible.
    Good: Dependency manifest found (distributions/requirements.txt).
  • doc
  • Images
  • intune
  • localization
  • msipackage
  • msixgluepackage
  • msixinstaller
  • nuget
  • src
  • storebroker
  • test
    Good: Test files detected (test).
  • tools
    Good: Environment pinned via tools/test/images/wslc-registry/Dockerfile.
  • triage
  • .clang-format
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .gdnsuppress
  • .gitignore
    Good: .gitignore present.
  • .vsconfig
  • cgmanifest.json
  • CMakeLists.txt
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • 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.
  • DATA_AND_PRIVACY.md
  • Directory.Build.Props
  • LICENSE
    Good: Licensed under MIT.
  • NOTICE.txt
  • nuget.config
  • packages.config
  • 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.
    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.
    Good: README documents how to run the project.
  • SECURITY.md
    Good: Security policy present.
  • SUPPORT.md
  • UserConfig.cmake.sample
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/microsoft/wsl)](https://www.repo-grade.com/report/microsoft/wsl)

More graded C++ repos