dotnet/eshop

0

/ 100

Documentation90
Engineering74
Health100
C#10,592MIT16d ago
Grade a repo

Popular and well-maintained. A little polish away from elite status.

A reference .NET application implementing an eCommerce site

Documentation

90

Contributing guide5pt79

Contributing guide is detailed and thorough.

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

74

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.

Tests18pt80

Test files detected (e2e/AddItemTest.spec.ts).

Reproducibility6pt82

Lockfile present (package-lock.json). Installs are reproducible.

CI/CD14pt85

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

Linting and formatting5pt100

.NET formatting configured (.editorconfig).

Project health

100

Dependency manifest6pt100

Dependency manifest found (package.json).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository files31 root entries
  • .aspire
  • .config
  • .devcenter
  • .github
    Good: CI is configured (.github/workflows/markdownlint.yml).
    Good: Dependabot configured for nuget.
  • build
  • e2e
    Good: Test files detected (e2e/AddItemTest.spec.ts).
  • img
  • src
  • tests
  • .editorconfig
    Good: .NET formatting configured (.editorconfig).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .markdownlint.json
  • .markdownlintignore
  • .spectral.yml
  • ci.yml
  • CODE-OF-CONDUCT.md
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Good: Contributing guide describes the PR/review workflow.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • Directory.Build.props
  • Directory.Build.targets
  • Directory.Packages.props
  • es-metadata.yml
  • eShop.slnx
  • eShop.Web.slnf
  • global.json
  • LICENSE
    Good: Licensed under MIT.
  • nuget.config
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • playwright.config.ts
  • 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.
    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.