phongnguyend/.net-developer-roadmap

0

/ 100

Documentation47
Engineering1
Health89
562MIT1d ago
Grade a repo

Getting noticed, but rough fundamentals could turn visitors away.

🚀 My Personal C# .NET Developer Roadmap & Asp.Net Core Developer Roadmap in 2026

Documentation

47

Install and run instructions9pt0

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

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.

README12pt65

README is present.

License6pt100

Licensed under MIT.

Engineering

1

Tests18pt0

No tests detected anywhere in the repository.

→ Add automated tests. They prove the code works and give contributors confidence to make changes.

CI/CD14pt0

No CI configuration detected in this repository.

→ If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.

Linting and formatting5pt0

No .NET formatter configured.

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

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.

Reproducibility6pt10

No dependency lockfile found (−70 pts).

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

Project health

89

Repository metadata5pt60

Repository has a description.

Dependency manifest6pt100

Dependency manifest found (examples/.Net 10/WhatsNewInNet10/AllowDuplicateJsonProperties/AllowDuplicateJsonProperties.csproj).

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)
  • 93
    Forks
  • 0
    Releases

Community

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

Responsiveness

  • 3d 11h
    Median issue response
  • <1h
    Median PR merge time
  • 3
    Open issues
Repository files11 root entries
  • code snippets
  • docs
    Good: Environment pinned via docs/Message Brokers/Kafka/kafka-single-node/docker-compose.yml.
  • examples
    Good: Dependency manifest found (examples/.Net 10/WhatsNewInNet10/AllowDuplicateJsonProperties/AllowDuplicateJsonProperties.csproj).
    Good: .gitignore present.
  • .net-developer-roadmap.png
  • .net-developer-roadmap.xml
  • aspnetcore-developer-roadmap.png
  • aspnetcore-developer-roadmap.xml
  • LICENSE
    Good: Licensed under MIT.
  • owasp-top-10.png
  • owasp-top-10.xml
  • README.md
    Good: README is present.
    Issue: README is fairly short (−10 pts). At 400+ chars you get partial credit; 1,500+ earns the full +20 pts.Fix: Expand with a description, install steps, usage, and examples.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    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.
    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.