Graphite

GraphiteEditor/Graphite

Community-built comprehensive 2D content creation appplication for graphic design, digital art, and interactive real-time motion graphics powered by a node-based procedural graphics engine

Ship status

Still shipping

Pushed in the last 30 days.

Last push
Oct 3, 2026
today
Ship score
88/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 26,874 → 27,383 (Aug 18 – Sep 29, 2026)
+355 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
27.4K
Forks
1.3K
Open issues
579
Watchers
132
Primary language
Rust
Created
Apr 26, 2020
Owner
GraphiteEditor · 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. 42 startups in the directory ship primarily in Rust.

Topics

#2d-graphics#animation#art#creative-coding#design#graphic-design#graphics#graphics-editor#image-manipulation#image-processing#motion-design#motion-graphics#node-graph#photo-editor#procedural#procedural-drawing#procedural-generation#svg-editor#vector-graphics

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 51%, self-hostable 34%, hosted offering 24%. 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: shipping — last push 2026-10-03This is the badge for GraphiteEditor/Graphite, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/GraphiteEditor/Graphite.svg)](https://ossean.com/GraphiteEditor/Graphite)

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.