Auth.js is now part of Better Auth · nextauthjs/next-auth · Discussion #13252 (original) (raw)

Auth.js is joining forces with Better Auth

We’re excited to share that Auth.js (formerly NextAuth.js) will now be maintained by the Better Auth team. Auth.js has powered authentication for a huge portion of the web, helping developers ship OAuth and session management fast. As applications and requirements grew more complex, the project’s original scope started to show its limits, and Better Auth emerged with a broader, more modern approach that aligns with where the ecosystem is heading.

We also want to acknowledge the obvious: our pace slowed over the past year. Maintainers moved roles, time was tight, and the surface area outgrew what we could responsibly support. This transition ensures that Auth.js continues to receive security and critical fixes, while giving users a clear, actively maintained path forward.

What this means for you: If you’re using Auth.js today, you can keep using it—maintenance will continue for security and urgent issues. If you’re starting something new (or planning a refresh), we recommend Better Auth as the best way forward for most teams, with migration guides available and more coming.

Finally, thank you to our community—contributors, maintainers, and everyone who opened issues, PRs, and discussions. You carried this project to this point and made a thoughtful transition possible. For more information and a better-auth migration guide, please check out their post here:
https://www.better-auth.com/blog/authjs-joins-better-auth

The Auth.js Team