gridea

getgridea/gridea

✍️ A static blog writing client (一个静态博客写作客户端)

Ship status

Gone silent

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

Last push
Jul 26, 2023
1,165 days ago
Stars, last 7 weeks
Stars, weekly: 10,257 → 10,239 (Aug 18 – Sep 29, 2026)
−8 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
10.2K
Forks
830
Open issues
585
Watchers
108
Primary language
TypeScript
Created
Mar 23, 2018
Owner
getgridea · 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. 208 startups in the directory ship primarily in TypeScript.

Topics

#blog#blog-engine#blog-platform#cms#electron#electronjs#gridea#jamstack#macos#static-blog#static-site#static-site-cms#static-site-generator#typescript#vue#vue2#windows

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 71%, self-hostable 36%, hosted offering 40%. 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 2023-07-26This is the badge for getgridea/gridea, as served from the URL below.
[![OSSEAN: silent](https://ossean.com/badge/getgridea/gridea.svg)](https://ossean.com/getgridea/gridea)

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.