nopCommerce

nopSolutions/nopCommerce

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

Ship status

Still shipping

Pushed in the last 30 days.

Last push
Oct 8, 2026
3 days ago
Ship score
84/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 10,155 → 10,160 (Sep 22 – Oct 6, 2026)
History starts 2026-09-22, the first weekly sample after this repo joined the directory.

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
10.2K
Forks
6K
Open issues
183
Watchers
585
Primary language
C#
License
Other
Created
Apr 9, 2014
Owner
nopSolutions · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. License unknown — GitHub’s own license field, not legal advice. 12 startups in the directory ship primarily in C#.

Topics

#asp-net#asp-net-core#aspnet#aspnetcore#cart#dotnet#dotnet-core#e-commerce#ecommerce#ecommerce-platform#headless#mvc#net10#net6#net7#net8#net9#shop#shopping-cart#sqlserver

How it got here

What the classifier decided, and when.

Classified as an open-source startup by Jev, TypeSafe’s classifier, on Sep 22, 2026 — os_startup 97%, self-hostable 86%, hosted offering 79%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.

Joined the directory 2026-09-22, found by the weekly discovery job at confidence 0.95. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: shipping — last push 2026-10-08This is the badge for nopSolutions/nopCommerce, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/nopSolutions/nopCommerce.svg)](https://ossean.com/nopSolutions/nopCommerce)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.