Skip to Content
better-auth-plugins

FAQ

Common questions about better-auth-plugins.

Is this part of better-auth?

No. These are community plugins, made to look and feel like better-auth's own, but not made or reviewed by the better-auth team. Report problems in this project's repository, not to better-auth.

Is there a warranty or support?

No. The plugins are provided as is, without warranty, under the MIT license. Test them in your own application like any other dependency. Report bugs in the repository's issues, and security problems privately (see below).

Which better-auth versions are supported?

better-auth and @better-auth/core 1.7.20 or a later 1.x release. The packages declare this range as peer dependencies; the tests run against both the lowest (1.7.20) and the newest release in it.

Which runtimes are supported?

Every runtime better-auth supports: Node.js, Bun, Deno, and edge runtimes. The plugins only use Web APIs (Web Crypto, fetch) and no node: modules. The Node 24 requirement in the repository is for developing the plugins, not for using them.

Can I use them with CommonJS?

The packages are ES modules only, like most of the current better-auth ecosystem. From CommonJS, load them with a dynamic import().

Why can't phone number, wallet, or Steam users sign up with the waitlist on?

They have generated emails, which are never on the waitlist. Put their domain in the waitlist's allow, or let their requests through with bypass, see Sign-up.

Do invited organization members skip the waitlist?

No. An organization invitation doesn't approve an email for the waitlist. Approve the invitee too (createInvite on the waitlist), or let the invitation's sign-up through with bypass.

Why isn't auth.api.addMember in the audit log?

addMember is server-only: it has no URL, so no plugin hook sees it. Record the event yourself with recordAuditEvent where you call it.

Where do I report a security problem?

Privately, not in a public issue. See the repository's security policy.

On this page