Popular for its size, but the engineering basics lag behind the interest.
Documentation
59
README documents how to install the project.
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.
README is present.
Licensed under MIT.
Engineering
53
No .NET formatter configured.
→ Add an .editorconfig to define C# formatting rules and run `dotnet format` in CI.
No dependency lockfile found (−70 pts).
→ Enable and commit packages.lock.json so NuGet restores are repeatable.
CI is configured (.github/workflows/backport.yml).
Test files detected (src/windowsdesktop/tests).
Issue or PR templates present.
Project health
84
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 manifest found (WindowsDesktop.sln).
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 67Forks
- 164Releaseslatest 5y ago
Community
- —Community health
- —authors own >50% of commits
- 210Watchers
Responsiveness
- 16hMedian issue response
- <1hMedian PR merge time
- 13Open issues
Repository files25 root entries
- .azuredevops
- .config
- .githubGood: CI is configured (.github/workflows/backport.yml).Good: Issue or PR templates present.
- eng
- srcGood: Test files detected (src/windowsdesktop/tests).
- .gitattributes
- .gitignoreGood: .gitignore present.
- azure-pipelines-PR.yml
- azure-pipelines.yml
- build.cmd
- Build.proj
- build.sh
- CODE-OF-CONDUCT.md
- CODEOWNERS
- CONTRIBUTING.mdIssue: 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
- LICENSEGood: Licensed under MIT.
- NuGet.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.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.slnGood: Dependency manifest found (WindowsDesktop.sln).