284,881 packages matching “custom-auth”
@custom-auth/prisma
v1.0.17 · 26 days ago
Prisma database adapter for @custom-auth.
No known vulnerabilities
@custom-auth/mongoose
v1.0.17 · 26 days ago
Mongoose database adapter for @custom-auth.
No known vulnerabilities
@custom-auth/adapter-nodemailer
v1.0.17 · 26 days ago
Nodemailer email adapter for @custom-auth.
No known vulnerabilities
@custom-auth/drizzle
v1.0.17 · 26 days ago
Drizzle ORM database adapter for @custom-auth.
No known vulnerabilities
@custom-auth/react
v1.0.17 · 26 days ago
React hooks and context providers for @custom-auth.
No known vulnerabilities
@custom-auth/core
v1.0.17 · 26 days ago
The framework-agnostic core engine for @custom-auth.
No known vulnerabilities
@custom-auth/adapter-resend
v1.0.17 · 26 days ago
Resend email adapter for @custom-auth.
No known vulnerabilities
@custom-auth/nextjs
v1.0.17 · 26 days ago
Edge-compatible Next.js helpers and middleware for @custom-auth.
No known vulnerabilities
@cedarjs/auth
v5.0.6 · 1 day ago
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P
No known vulnerabilities
@cedarjs/auth-clerk-api
v5.0.6 · 1 day ago
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P
No known vulnerabilities
@cedarjs/auth-clerk-setup
v5.0.6 · 1 day ago
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P
No known vulnerabilities
@cedarjs/auth-clerk-web
v5.0.6 · 1 day ago
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P
No known vulnerabilities
harshil-auth
v2.6.9 · 6 months ago
Custom auth library
No known vulnerabilities
@aws-blocks/auth-common
v0.1.3 · 1 month ago
Shared interfaces and UI components for all AWS Blocks auth Building Blocks. Use this package to build provider-agnostic auth UI, or import the types when authoring a custom auth Building Block.
No known vulnerabilities
@cedarjs/auth-auth0-api
v5.0.6 · 1 day ago
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P
No known vulnerabilities
@cedarjs/auth-auth0-setup
v5.0.6 · 1 day ago
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P
No known vulnerabilities
@cedarjs/auth-auth0-web
v5.0.6 · 1 day ago
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P
No known vulnerabilities
@apicrafthq/script-sdk
v0.1.0-beta.0 · 22 days ago
TypeScript types for API Craft middleware and custom-auth scripts.
No known vulnerabilities
@cedarjs/auth-azure-active-directory-setup
v5.0.6 · 1 day ago
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P
No known vulnerabilities
@cedarjs/auth-supabase-api
v5.0.6 · 1 day ago
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P
No known vulnerabilities