241,433 packages matching “custom claims”
@connectid-tools/idp-selector-react
v6.12.5 · 3 days ago
React component for IDP Selector.
No known vulnerabilities
@cedarjs/auth-clerk-web
v5.0.6 · 18 days 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
@boxyhq/saml20
v1.16.0 · 1 month ago
SAML 2.0 token parser for Node.js
No known vulnerabilities
pumpfun-claims-bot
v1.0.4 · 16 days ago
PumpFun on-chain intelligence — Telegram feed + MCP server for AI assistants. Query token data, GitHub social fee claims, creator profiles, and more.
No known vulnerabilities
@nodii/db-rls
v0.14.0 · 14 days ago
Three-pool RLS dispatch + GUC-set + entry-point helpers + RLS policy DDL generator for the Nodii microservice stack. Polyglot per D159 (TS + Python + Go). Spec: planning hub docKey=db-rls.
No known vulnerabilities
@cedarjs/auth-auth0-api
v5.0.6 · 18 days 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-dbauth-web
v5.0.6 · 18 days 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-netlify-setup
v5.0.6 · 18 days 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
remark-heading-id
v1.0.1 · 2 years ago
The remark plugin for supporting custom heading id also including default id
No known vulnerabilities
@angular-builders/custom-esbuild
v22.0.1 · 1 month ago
Custom esbuild builders for Angular build facade. Allow to modify Angular build configuration without ejecting it
No known vulnerabilities
@cedarjs/auth-auth0-web
v5.0.6 · 18 days 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 · 18 days 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
@redwoodjs/auth
v8.9.0 · 10 months ago
## Contributing
No known vulnerabilities
@cedarjs/auth-supertokens-setup
v5.0.6 · 18 days 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-dbauth-api
v5.0.6 · 18 days 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
@ungap/custom-elements
v1.3.0 · 3 years ago
All inclusive customElements polyfill for every browser
No known vulnerabilities
@cedarjs/auth-supabase-api
v5.0.6 · 18 days 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-setup
v5.0.6 · 18 days 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-supertokens-web
v5.0.6 · 18 days 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-azure-active-directory-api
v5.0.6 · 18 days 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