npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

access-right

v2.0.3

Published

A tiny helper library to handle access rights in your node backend

Downloads

143

Readme

access-right

Build Status npm version

This tiny library helps you to check if a user has access to somethin (e.g. a resource) in your node app. I created this lib to make my life a bit easier, when working with user and rights.

Probably this is not useful for anybody else, but who knows?

user-rights?

If you have an application with users they probably have different access levels oder rights. I prefer a hierarchic user-level approach. Every user-right is a string with 0..n 'dots'. Every dot in the string represents a hierarchy level. The more dots, the lower is the right in the hierarchy (similiar to how domain and subdomains and sub-subdomains [...] work).

A user is granted access to a resource if one of these conditions is true:

  • the user has exactly the correct access right (required right is equal to provided right)
  • the user has a right that is higher in the hierarchy than the required right

WAT?

Let's look at an example:

userA has the following rights: ['some', 'foo.bar'] userB has the following rights: ['other', 'foo.bar.wat']

Assume we have the following resources:

resourceA which requires: ['some'] resourceB which requires: ['foo.bar.wat'] resourceC which requires: ['foo']

Who can access what?

userA can access resourceA and resourceB, but not resourceC userA has access to resourceA, because she has the exactly matching right (some) that is required to access the resource. She can access resourceB, because she has a right that is higher in the hierarchy than the right that is required to access the resource (has: foo.bar, required: foo.bar.wat) userA cannot access resourceC, because she only has a right that is lower in the hierarchy than the right the resource requires.

userB can only access resourceB (because the required right foo.bar.wat matches exactly one of the provided rights)

tests

There are some basic unit tests. Run them with npm:

npm install
npm test