SaaSHub helps you find the best software and product alternatives Learn more →
Top 15 TypeScript Permission Projects
-
SurveyJS
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.
-
node-casbin
An authorization library that supports access control models like ACL, RBAC, ABAC in Node.js and Browser
-
ngx-permissions
Permission and roles based access control for your angular(angular 2,4,5,6,7,9+) applications(AOT, lazy modules compatible
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
vue-simple-acl
A simple unopinionated Vue plugin for managing user roles and permissions, access-control list (ACL) and role-based access control (RBAC).
-
slauth-cli
CLI that scans directories for Cloud Provider SDK usage generates the IAM Policies/Permissions needed
-
playground
Playground for SpiceDB, the open source, Google Zanzibar-inspired permissions database to enable fine-grained access control for customer applications (by authzed)
-
warrant-express-middleware
Expressjs Middleware for enforcing access control on API endpoints using the Warrant API
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
Project mention: Launch HN: Slauth (YC S22) – auto-generate secure IAM policies for AWS and GCP | news.ycombinator.com | 2023-12-04Hi HN, We're Daniel and Bruno and working on [Slauth.io]([https://slauth.io/](https://slauth.io/)). Slauth.io is a CLI to auto-generate secure IAM policies for AWS, and GCP (Azure in the next few days!). We enable development teams to speed up creating secure policies and reduce over-permissive policies being deployed to the cloud.
Check out the [video](https://www.loom.com/share/bd02211659eb4c7f9b335e34094b57cb?...) or give our open-source CLI a try with one of the sample repo's on [GitHub]([https://github.com/slauth-io/slauth-cli](https://github.com/...)
We got into the cloud access market by coincidence and were amazed by the amount of money spent on IAM. Current tooling such as [Ermetic.com]([http://Ermetic.com](http://ermetic.com/)) and [Wiz.io]([http://Wiz.io](http://wiz.io/)) visualize IAM misconfigurations post deployment but don't actually change engineering behavior, leaving organizations in a constant loop of engineers deploying over-permissive policies ⇒ security engineers/CISO's getting alerts ⇒ Jira tickets created begging developers to remediate ⇒ New over-permissive policies being deployed again.
We interviewed hundreds of developers and DevOps engineers and discovered two key pain points:
1. *IAM is a Hassle:* Developers despise dealing with IAM intricacies.
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
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.
TypeScript Permissions related posts
-
SpiceDB Playground is now Open Source
-
Three Ways to Secure Database APIs: Which Is Right for You?
-
How can GraphQL Shield play nicely with Type Based Error Handling?
-
Building RBAC in Node
-
GraphQL AuthZ - GraphQL Authorization layer
-
Manage complex permissions/access rights
-
Node Authorization Framework
-
A note from our sponsor - SaaSHub
www.saashub.com | 4 May 2024
Index
What are some of the best open-source Permission projects in TypeScript? This list will help you:
Project | Stars | |
---|---|---|
1 | deepstream.io | 7,128 |
2 | graphql-shield | 3,512 |
3 | node-casbin | 2,482 |
4 | accesscontrol | 2,118 |
5 | nest-access-control | 1,060 |
6 | ngx-permissions | 922 |
7 | react-role | 182 |
8 | vue-simple-acl | 123 |
9 | slauth-cli | 70 |
10 | update-github-actions-permissions | 62 |
11 | nuxt-permissions | 46 |
12 | playground | 26 |
13 | iamjs | 21 |
14 | gitcloud | 12 |
15 | warrant-express-middleware | 3 |
Sponsored