0
/ 100
Popular and well-maintained. A little polish away from elite status.
A reference .NET application implementing an eCommerce site
Top 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 lint step to catch style issues automatically.
- 3CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- 4CI/CD14pt
Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
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
90
Contributing guide is detailed and thorough.
README is present.
README documents how to install the project.
Licensed under MIT.
Engineering
74
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.
Test files detected (e2e/AddItemTest.spec.ts).
Lockfile present (package-lock.json). Installs are reproducible.
CI is configured (.github/workflows/markdownlint.yml).
.NET formatting configured (.editorconfig).
Project health
100
Dependency manifest found (package.json).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository files31 root entries
- .aspire
- .config
- .devcenter
- .githubGood: CI is configured (.github/workflows/markdownlint.yml).Good: Dependabot configured for nuget.
- build
- e2eGood: Test files detected (e2e/AddItemTest.spec.ts).
- img
- src
- tests
- .editorconfigGood: .NET formatting configured (.editorconfig).
- .gitattributes
- .gitignoreGood: .gitignore present.
- .markdownlint.json
- .markdownlintignore
- .spectral.yml
- ci.yml
- CODE-OF-CONDUCT.md
- CONTRIBUTING.mdGood: 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
- LICENSEGood: Licensed under MIT.
- nuget.config
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- package.jsonGood: Dependency manifest found (package.json).
- playwright.config.ts
- README.mdGood: 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.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/dotnet/eshop)