filmcraft

storytold/filmcraft

FilmCraft: An open-source, nonlinear video editor written by scratch in pure Rust

Ship status

Still shipping

Pushed in the last 30 days.

Last push
Nov 1, 2026
today
Ship score
100/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 11,618 → 16,424 (Oct 13 – Oct 27, 2026)
History starts 2026-10-13, 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
17.1K
Forks
7.1K
Open issues
1.8K
Watchers
83
Primary language
Rust
Created
Sep 30, 2026
Owner
storytold · 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. 47 startups in the directory ship primarily in Rust.

Topics

#art#rust#video#video-editing#video-editor#video-processing

How it got here

What the classifier decided, and when.

Classified as an open-source startup by Jev, TypeSafe’s classifier, on Oct 12, 2026 — os_startup 93%, self-hostable 49%, hosted offering 21%. 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-10-12, found by the weekly discovery job at confidence 0.91. 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-11-01This is the badge for storytold/filmcraft, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/storytold/filmcraft.svg)](https://ossean.com/storytold/filmcraft)

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.