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

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

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

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

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

Deterministic policy evaluation and Cedar/OPA mappings for Axtary agent actions.

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

Array manipulation, ordering, searching, summarizing, etc.

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

WASM bindings and typescript types for Cedar lib

Drizzle ORM policy store, schema factory and query-plan-to-SQL compiler for @nestm/permissions.

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

Email, SMS & phone-call infrastructure for AI agents — real email addresses, phone numbers, and agent-driven outbound voice calls

Tool for transforming styles with JS plugins

React components for editing Cedar policies, schemas, and context using Monaco Editor

Merge Tailwind CSS classes without style conflicts

Framework-free Cedar authorization engine, policy-store SPI and query-plan AST for @nestm/permissions.

View docs [here](https://radix-ui.com/primitives/docs/utilities/slot).

The tiniest and the fastest library for terminal output formatting with ANSI colors

Shared utilities for CedarJS packages and apps