353,612 packages matching “dh role based access”
@cedarjs/auth-supabase-api
v5.0.6 · 15 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-firebase-web
v5.0.6 · 15 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-azure-active-directory-api
v5.0.6 · 15 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-setup
v5.0.6 · 15 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-firebase-setup
v5.0.6 · 15 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
@vly-ai/integrations
v0.6.12 · 2 months ago
Access AI models, email services, and project thumbnail capture through vly.ai and freebuff.com without managing multiple API keys or accounts
No known vulnerabilities
@cedarjs/auth-supertokens-api
v5.0.6 · 15 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-setup
v5.0.6 · 15 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 · 15 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-web
v5.0.6 · 15 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 · 15 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 · 15 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-web
v5.0.6 · 15 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
@spectrum-web-components/alert-dialog
v1.12.2 · 1 month ago
Web component implementation of a Spectrum design AlertDialog
No known vulnerabilities
nodebb-plugin-sso-oauth2-multiple
v2.0.0 · 1 month ago
NodeBB Multiple OAuth2 SSO
No known vulnerabilities
@azure/arm-resources
v8.0.0 · 1 month ago
A generated SDK for ResourceManagementClient.
No known vulnerabilities
@zoom/appssdk
v0.16.41 · 9 days ago
Zoom Apps SDK
No known vulnerabilities
@adobe/aio-lib-target
v4.0.3 · 4 months ago
Adobe Target SDK
No known vulnerabilities
simple-access
v2.0.5 · 5 months ago
Attribute-Role-Based Hybrid Access Control Library
No known vulnerabilities