0
/ 100
Early-stage engineering. The fastest wins are setup instructions and CI.
The shared-nothing io_uring runtime for .NET
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 (70).
See your top fixesTop fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.
- 2CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3CI/CD14pt
Add a lint step to catch style issues automatically.
- 4CI/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.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
41
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).
→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.
README is present.
Licensed under MIT.
Engineering
47
No .NET formatter configured.
→ Add an .editorconfig to define C# formatting rules and run `dotnet format` in CI.
No issue or PR templates found (−100 pts).
→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.
No dependency lockfile found (−70 pts).
→ Enable and commit packages.lock.json so NuGet restores are repeatable.
CI is configured (.github/workflows/build.yml).
Test files detected (Research/Tests).
Project health
100
Dependency manifest found (Playground/AspNet/Playground.AspNet.csproj).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 19 / 117Commits (30d / 90d)
- 6Forks
- 1Releaseslatest 3mo ago
Community
- 42% - WeakCommunity health
- -authors own >50% of commits
- 48Watchers
Responsiveness
- 19d 23hMedian issue response
- <1hMedian PR merge time
- 34Open issues
Repository files16 root entries
- .githubGood: CI is configured (.github/workflows/build.yml).
- bench
- docs
- fuzz
- PlaygroundGood: Environment pinned via Playground/Dockerfile.Good: Dependency manifest found (Playground/AspNet/Playground.AspNet.csproj).
- ResearchGood: Test files detected (Research/Tests).
- scripts
- src
- tests
- .dockerignore
- .gitattributes
- .gitignoreGood: .gitignore present.
- global.json
- ioxide.slnx
- LICENSEGood: Licensed under MIT.
- README.mdGood: README is present.Issue: README has some structure (−7 pts). 2-3 headings earns partial credit; 4+ earns the full +15 pts.Fix: Add more sections (Overview, Install, Usage, Contributing) using ## headings.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.Good: README includes status badges.Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/mda2av/ioxide)