A powerful authorization library for Node.js and browser environments supporting ACL, RBAC, and ABAC access control models.
Node-Casbin is an authorization library for Node.js and browser environments that enforces access control policies based on configurable models like ACL, RBAC, and ABAC. It provides a unified interface to manage and check permissions, helping developers implement consistent security logic across their applications.
Node.js developers and frontend engineers building applications that require fine-grained authorization, such as enterprise systems, multi-tenant platforms, or any project needing role-based or attribute-based access control.
Developers choose Node-Casbin for its model flexibility, production-ready stability, and comprehensive feature set that supports multiple access control paradigms without locking them into a single approach. Its integration with the broader Casbin ecosystem ensures consistency and reliability.
An authorization library that supports access control models like ACL, RBAC, ABAC in Node.js and Browser
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports ACL, RBAC, and ABAC through configurable models, allowing developers to switch between access control paradigms without changing libraries, as highlighted in the README's key features.
Provides both low-level Management API and user-friendly RBAC API for dynamic permission updates, enabling real-time adjustments to security rules without restarting services.
Part of the stable Casbin ecosystem with implementations across multiple languages, ensuring reliable and uniform authorization logic in polyglot environments, as shown in the supported languages table.
Includes watchers for policy synchronization across service instances, supporting distributed systems and preventing consistency issues in microservices architectures.
Requires separate model and policy files for setup, which adds initial overhead compared to inline authorization code, and the README directs users to external resources for details.
Policy persistence with databases or other storage relies on additional adapters, increasing integration effort and potential points of failure, as noted in the adapters documentation link.
Core documentation is hosted externally on casbin.org, which may lead to outdated or less accessible information compared to integrated docs, requiring extra verification from users.