reactive-resume

AmruthPillai/Reactive-Resume · now at reactive-resume/reactive-resume

A one-of-a-kind resume builder that keeps your privacy in mind. Completely secure, customizable, portable, open-source and free forever. Try it out today!

Ship status

Still shipping

Pushed in the last 30 days.

Last push
Oct 9, 2026
today
Ship score
99/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 41,729 → 43,849 (Aug 25 – Oct 6, 2026)
+1,557 stars in the 28 days to 2026-10-06

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
44K
Forks
4.8K
Open issues
37
Watchers
135
Primary language
TypeScript
Created
Mar 25, 2020
Owner
reactive-resume · 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. 213 startups in the directory ship primarily in TypeScript.

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 95%, self-hostable 70%, hosted offering 33%. 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-09This is the badge for AmruthPillai/Reactive-Resume, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/AmruthPillai/Reactive-Resume.svg)](https://ossean.com/AmruthPillai/Reactive-Resume)

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.