supertokens-core

supertokens/supertokens-core

Open source alternative to Auth0 / Firebase Auth / AWS Cognito

Ship status

Still shipping

Pushed in the last 30 days.

Last push
Oct 6, 2026
3 days ago
Ship score
83/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 15,277 → 15,332 (Aug 25 – Oct 6, 2026)
+37 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
15.3K
Forks
835
Open issues
157
Watchers
100
Primary language
Java
License
Other
Created
Jan 5, 2020
Owner
supertokens · Organization

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. 34 startups in the directory ship primarily in Java.

Topics

#auth0#authentication#aws-cognito#email-password#email-password-login#firebase-auth#hacktoberfest#java#keycloak#login#oauth#password#passwordless#passwordless-authentication#passwordless-login#session-management#signin#social-login#supertokens

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 90%, self-hostable 85%, hosted offering 83%. 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-06This is the badge for supertokens/supertokens-core, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/supertokens/supertokens-core.svg)](https://ossean.com/supertokens/supertokens-core)

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.