Top 6 TypeScript Role Projects

accesscontrol

9 2,118 0.0 TypeScript

Role and Attribute based Access Control for Node.js
ngx-permissions

4 920 4.9 TypeScript

Permission and roles based access control for your angular(angular 2,4,5,6,7,9+) applications(AOT, lazy modules compatible
SurveyJS

surveyjs.io sponsored

Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
nuxt-permissions

1 46 6.0 TypeScript

Nuxt module for permission management
nest-e-commerce-boilerplate

1 30 1.8 TypeScript

Backend for Ecommerce platform using Nest + PostgreSQL + TypeORM
iamjs

4 21 8.5 TypeScript

iamjs - Your complete Access Control Library with End-to-end typesafety

Project mention: The TypeScript Access Control Library for Unmatched Typesafety | news.ycombinator.com | 2023-09-04

"iamjs" - the game-changing TypeScript Access Control Library is here!
Tired of authorization headaches? Look no further! iamjs is the complete solution you've been waiting for. With its unparalleled typesafety and end-to-end functionality, iamjs makes authorization a breeze for both Node.js and browser environments.
Featuring support for popular frameworks like express, koa, next.js, and react, iamjs is versatile and adaptable to your project's needs. Choose from a range of packages:
@iamjs/express - Express middleware that simplifies authorization workflows @iamjs/koa - Koa middleware for seamless authorization integration @iamjs/next - Next.js middleware for effortless authorization management @iamjs/react - React component for hassle-free authorization implementation
And that's not all! For maximum flexibility, you can also opt for the @iamjs/core package, which contains all the necessary logic and can be seamlessly integrated with any framework of your choice.
Don't waste time on complex authorization setups anymore. Join the iamjs revolution now and experience the power of typesafety combined with effortless authorization management!
Check out iamjs on GitHub: https://github.com/triyanox/iamjs

gitcloud

1 12 4.2 TypeScript

Example application using Oso Cloud

Project mention: Authorization is still a nightmare for engineers | news.ycombinator.com | 2024-04-16

> However: you seem to target developers. Why do you force me to leave my IDE and use your "rules editor"? Can I not write all those things in my IDE, with all the support it brings, and integrate this into my CICD flow? (yes, there is the .polar file, but why force me to jump through hoops?)
Hey valenterry! Oso CTO here. You can absolutely write policies locally and integrate this with CI/CD. We have vscode extension for the former, and CI tools for running local dev environments and CI for running this locally or in CI or whatever.
The UI is mostly nice for getting started development experience, e.g. it integrates directly with Oso Cloud without needing to configure credentials.
> Then, why did you create a new DSL and not a merely a (de-)serializable datastructure (which will indeed look like a dsl)? One, that is powerful enough to represent the capabilities you need. Then, I could in fact use any language (library) of my choice and create the rules from this language, which just has to create the datastructure.
We have a post on this coming soon! The short version is that Polar is a logic language based on Prolog/Datalog/miniKanren. And logic languages are a particularly good fit for representing the branching conditional logic you often see in authorization configurations.
And it made it easier for us to do custom work like add inline policy tests.
> Apart from that, I really like the `yes, if` idea! Would be nice to hear a bit more about that (unfortunately, the article pretty much ends there). Such as: how to deal with actions that change things and can (or must) potentially be run before the authorization is completed and such.
We typically recommend authorizing in two places: at the start of a request, and then when fetching data.
e.g. in our demo app, authorizing "can a user create an issue" involves authorizing a "create_issue" action against the repository itself: https://github.com/osohq/gitcloud/blob/sam/list-filtering/se...
Whereas anything listing issues calls the `list_local` method and does the `yes, if` style approach.

NOTE: The open source projects on this list are ordered by number of github stars. The number of mentions indicates repo mentiontions in the last 12 Months or since we started tracking (Dec 2020).