Popular and well-maintained. A little polish away from elite status.

Windows Subsystem for Linux

Documentation

82

README12pt70

README is present.

Contributing guide5pt77

Contributing guide is detailed and thorough.

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 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.
    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.
    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