57
/ 100
Popular for its size, but the engineering basics lag behind the interest.
Tool to inspect .NET assets, like docker inspect.
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 (72).
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
48
No license detected.
→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.
Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).
→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.
README is present.
README documents how to install the project.
Engineering
46
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.
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.
CI is configured (.github/workflows/ci.yml).
Test files detected (src/DotnetInspector.Services.Tests/DependencyResolutionServiceTests.cs).
Project health
100
Dependency manifest found (src/DotnetInspector.Core/DotnetInspector.Core.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
- -Commits (30d / 90d)
- 8Forks
- 52Releaseslatest 5mo ago
Community
- 28% - WeakCommunity health
- 1 bus factorlowauthor own >50% of commits
- 136Watchers
Responsiveness
- 6hMedian issue response
- <1hMedian PR merge time
- 18Open issues
Repository files26 root entries
- .claude
- .claude-plugin
- .githubGood: CI is configured (.github/workflows/ci.yml).
- docs
- eng
- prompts
- scripts
- skills
- srcGood: Test files detected (src/DotnetInspector.Services.Tests/DependencyResolutionServiceTests.cs).Good: Dependency manifest found (src/DotnetInspector.Core/DotnetInspector.Core.csproj).
- taste
- tests
- tools
- .dotnet-install.json
- .gitignoreGood: .gitignore present.
- .markdownlint.yaml
- AGENTS.md
- backlog.md
- Directory.Build.props
- Directory.Build.targets
- Directory.Packages.props
- install-source.sh
- install.ps1
- install.sh
- 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.Good: README has code examples.Issue: No live demo link in the README (−20 pts).Fix: Link to a deployed version, docs site, or demo video. Users want to see it running.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.
- THIRD-PARTY-NOTICES.TXT
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/richlander/dotnet-inspect)