Strong community interest, but docs and engineering haven't caught up to the hype.

Simple, unambitious mediator implementation in .NET

Documentation

69

Contributing guide5pt0

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.

Install and run instructions9pt45

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under Other.

Engineering

56

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 (test).

Linting and formatting5pt100

.NET formatting configured (.editorconfig).

Project health

100

Dependency manifest6pt100

Dependency manifest found (samples/MediatR.Examples.AspNetCore/MediatR.Examples.AspNetCore.csproj).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository files17 root entries
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
  • assets
  • samples
    Good: Dependency manifest found (samples/MediatR.Examples.AspNetCore/MediatR.Examples.AspNetCore.csproj).
  • src
  • test
    Good: Test files detected (test).
  • .editorconfig
    Good: .NET formatting configured (.editorconfig).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • Build.ps1
  • BuildContracts.ps1
  • Directory.Build.props
  • LICENSE.md
    Good: Licensed under Other.
  • MediatR.slnx
  • MediatR.snk
  • NuGet.Config
  • Push.ps1
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    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.