richlander/dotnet-inspect

0

/ 100

Documentation48
Engineering46
Health100
C#1351d ago
Grade a repo

Popular for its size, but the engineering basics lag behind the interest.

Tool to inspect .NET assets, like docker inspect.

Documentation

48

License6pt0

No license detected.

→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.

Contributing guide5pt25

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.

README12pt50

README is present.

Install and run instructions9pt90

README documents how to install the project.

Engineering

46

Linting and formatting5pt0

No .NET formatter configured.

→ Add an .editorconfig to define C# formatting rules and run `dotnet format` in CI.

Reproducibility6pt0

No dependency lockfile found (−70 pts).

→ Enable and commit packages.lock.json so NuGet restores are repeatable.

Issue and PR templates6pt0

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/CD14pt57

CI is configured (.github/workflows/ci.yml).

Tests18pt80

Test files detected (src/DotnetInspector.Services.Tests/DependencyResolutionServiceTests.cs).

Project health

100

Dependency manifest6pt100

Dependency manifest found (src/DotnetInspector.Core/DotnetInspector.Core.csproj).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 8
    Forks
  • 52
    Releaseslatest 4mo ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 135
    Watchers

Responsiveness

  • 6h
    Median issue response
  • <1h
    Median PR merge time
  • 8
    Open issues
Repository files26 root entries
  • .claude
  • .claude-plugin
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
  • docs
  • eng
  • prompts
  • scripts
  • skills
  • src
    Good: 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
  • .gitignore
    Good: .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.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.
    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