reaction

reactioncommerce/reaction

Project has been discontinued ////// Mailchimp Open Commerce is an API-first, headless commerce platform built using Node.js, React, GraphQL. Deployed via Docker and Kubernetes.

Ship status

Gone silent

No push in over 120 days. A quiet repo may also be a finished one.

Last push
Mar 1, 2026
215 days ago
Ship score
10/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 12,399 → 12,402 (Aug 18 – Sep 29, 2026)
+2 stars in the 28 days to 2026-09-29

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
12.4K
Forks
2.2K
Open issues
96
Watchers
419
Primary language
JavaScript
Created
Sep 18, 2013
Owner
reactioncommerce · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license — GitHub’s own license field, not legal advice. 57 startups in the directory ship primarily in JavaScript.

Topics

#cart#commerce#docker#e-commerce#ecommerce#ecommerce-platform#graphql#hacktoberfest#headless#javascript#marketplace#mongodb#reaction-action#reactioncommerce#shop#storefront

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 80%, self-hostable 68%, hosted offering 43%. 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.

Listed since the 2025-09 crawl. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: silent — last push 2026-03-01This is the badge for reactioncommerce/reaction, as served from the URL below.
[![OSSEAN: silent](https://ossean.com/badge/reactioncommerce/reaction.svg)](https://ossean.com/reactioncommerce/reaction)

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.