nopsolutions/nopcommerce
Grade a repo

76

/ 100

GradeC

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

Top 38% of 5,156 graded repos

ASP.NET Core eCommerce software. nopCommerce is a free and open-source shopping cart.

Documentation68
Engineering74
Health94
C#10,094Other1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

17 to address
  1. 1
    Tests18pt

    Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.

  2. 2
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  3. 3
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

  4. 4
    CI/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.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

68

Install and run instructions9pt45

README documents how to install the project.

Contributing guide5pt52

CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

README12pt75

README is present.

License6pt100

Licensed under Other.

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 (src/Tests).

Reproducibility6pt80

Lockfile present (src/Presentation/Nop.Web/package-lock.json). Installs are reproducible.

CI/CD14pt85

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

Linting and formatting5pt100

.NET formatting configured (.editorconfig).

Project health

94

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt100

Dependency manifest found (src/Build/src/ClearPluginAssemblies.sln).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • 26 / 97
    Commits (30d / 90d)
  • 5,993
    Forks
  • 77
    Releaseslatest 10y ago

Community

  • 75% - Good
    Community health
  • 2 bus factor
    authors own >50% of commits
  • 10,094
    Watchers

Responsiveness

  • 489d 5h
    Median issue response
  • <1h
    Median PR merge time
  • 168
    Open issues
Repository files18 root entries
  • .github
    Good: CI is configured (.github/workflows/dotnet.yml).
  • src
    Good: Test files detected (src/Tests).
    Good: Lockfile present (src/Presentation/Nop.Web/package-lock.json). Installs are reproducible.
    Good: Dependency manifest found (src/Build/src/ClearPluginAssemblies.sln).
    Issue: Build artifacts or local files may be committed (src/Presentation/Nop.Web/wwwroot/lib_npm/datatables.net-buttons-bs4/node_modules/datatables.net-bs4) (−40 pts).Fix: Remove them and add to .gitignore.
  • upgradescripts
  • .dockerignore
  • .editorconfig
    Good: .NET formatting configured (.editorconfig).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Issue: CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    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).
    Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • docker-compose.yml
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • global.json
  • ISSUE_TEMPLATE.md
  • LICENSE.md
    Good: Licensed under Other.
  • mysql-docker-compose.yml
  • postgresql-docker-compose.yml
  • README.md
    Good: README is present.
    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.
    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.
  • SECURITY.md
    Good: Security policy present.
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/nopsolutions/nopcommerce)](https://www.repo-grade.com/report/nopsolutions/nopcommerce)

More graded C# repos