decap-cms

decaporg/decap-cms

A Git-based CMS for Static Site Generators

Ship status

Still shipping

Pushed in the last 30 days.

Last push
Oct 2, 2026
today
Ship score
97/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 19,301 → 19,406 (Aug 18 – Sep 29, 2026)
+77 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
19.4K
Forks
3.1K
Open issues
608
Watchers
244
Primary language
JavaScript
Created
Jan 20, 2015
Owner
decaporg · 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

#cms#content-management-system#decap-cms#git-based-cms#headless-cms#jamstack#javascript#netlify-cms#npm-package#react#static#static-site#static-site-generator

How it got here

What the classifier decided, and when.

Read by Jev, TypeSafe’s classifier, on Sep 22, 2026, which did not call this an open-source startup — it chose a package or library instead, and put os_startup at 16% (self-hostable 58%, hosted offering 37%). 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. This one is in that queue, waiting for a person — removing a listing is a pull request a human opens.

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: shipping — last push 2026-10-02This is the badge for decaporg/decap-cms, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/decaporg/decap-cms.svg)](https://ossean.com/decaporg/decap-cms)

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.