inbox-zero

elie222/inbox-zero

The world's best AI personal assistant for email. Open source app to help you reach inbox zero fast.

Ship status

Still shipping

Pushed in the last 30 days.

Last push
Oct 11, 2026
today
Ship score
96/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 12,281 → 12,421 (Sep 22 – Oct 6, 2026)
History starts 2026-09-22, 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
12.4K
Forks
1.6K
Open issues
160
Watchers
47
Primary language
TypeScript
License
Other
Created
Jul 12, 2023
Owner
elie222 · User

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. License unknown — GitHub’s own license field, not legal advice. 213 startups in the directory ship primarily in TypeScript.

Topics

#ai#email#gmail#loops#nextjs#openai#postgresql#posthog#prisma#productivity#resend#shadcn-ui#tailwind#tinybird#turborepo#typescript#upstash

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 100%, self-hostable 46%, hosted offering 59%. 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-09-22, found by the weekly discovery job at confidence 0.99. 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-11This is the badge for elie222/inbox-zero, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/elie222/inbox-zero.svg)](https://ossean.com/elie222/inbox-zero)

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.