Popular and well-maintained. A little polish away from elite status.
Windows Subsystem for Linux
Documentation
82
README12pt
70
README is present.
Contributing guide5pt
77
Contributing guide is detailed and thorough.
Install and run instructions9pt
90
README documents how to install the project.
License6pt
100
Licensed under MIT.
Engineering
78
CI/CD14pt
57
CI is configured (.github/workflows/distributions.yml).
Tests18pt
80
Test files detected (test).
Reproducibility6pt
80
Lockfile present (distributions/requirements.txt). Installs are reproducible.
Linting and formatting5pt
100
Linter or formatter configured (.editorconfig).
Issue and PR templates6pt
100
Issue or PR templates present.
Project health
100
Dependency manifest6pt
100
Dependency manifest found (distributions/requirements.txt).
Repository metadata5pt
100
Repository has a description.
Activity5pt
100
Actively maintained (pushed within the last month).
Housekeeping3pt
100
.gitignore present.
Repository files39 root entries
- .config
- .githubGood: CI is configured (.github/workflows/distributions.yml).Good: Issue or PR templates present.
- .pipelines
- cloudtest
- cmake
- diagnostics
- distributionsGood: 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
- testGood: Test files detected (test).
- toolsGood: Environment pinned via tools/test/images/wslc-registry/Dockerfile.
- triage
- .clang-format
- .editorconfigGood: Linter or formatter configured (.editorconfig).
- .gdnsuppress
- .gitignoreGood: .gitignore present.
- .vsconfig
- cgmanifest.json
- CMakeLists.txt
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- CONTRIBUTING.mdGood: 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
- LICENSEGood: Licensed under MIT.
- NOTICE.txt
- nuget.config
- packages.config
- README.mdGood: 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.mdGood: Security policy present.
- SUPPORT.md
- UserConfig.cmake.sample