379,316 packages matching “cedar-docs”
@docknetwork/vc-delegation-engine
v1.0.4 · 3 months ago
A focused Javascript engine for evaluating delegated credentials in Verifiable Presentations, extracting authorized claims, and piping the resulting facts into Cedar policy decisions.
No known vulnerabilities
@cedarjs/auth-firebase-api
v6.0.0 · 14 hours 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
v6.0.0 · 14 hours 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-api
v6.0.0 · 14 hours 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-api
v6.0.0 · 14 hours 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/pg
v0.1.0-alpha.1 · 20 days ago
Worktree-isolated local Postgres for Vite+, Nx, and CedarJS (via autopg)
No known vulnerabilities
@cedarjs/auth
v6.0.0 · 14 hours 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
v6.0.0 · 14 hours 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
v6.0.0 · 14 hours 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
@swornsystems/tree-sitter-cedar
v0.12.0 · 22 days ago
Cedar grammars for tree-sitter
No known vulnerabilities
@cedarjs/auth-auth0-setup
v6.0.0 · 14 hours 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
v6.0.0 · 14 hours 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
v6.0.0 · 14 hours 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
v6.0.0 · 14 hours 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
v6.0.0 · 14 hours 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
v6.0.0 · 14 hours 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
@nestm/permissions-typeorm
v0.1.0-alpha.1 · 22 days ago
TypeORM policy store and query-plan-to-SQL compiler for @nestm/permissions.
No known vulnerabilities
@cedarjs/auth-supabase-setup
v6.0.0 · 14 hours 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
cedar-model-typescript-library
v1.0.2 · 2 days ago
CEDAR Model Typescript Library - a library to work with fields, elements, templates and instances implemented in TypeScript
No known vulnerabilities
@cedarjs/auth-supertokens-setup
v6.0.0 · 14 hours 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