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

nod

v0.2.0

Published

A simple, persistence-agnostic authorization system for node.js

Downloads

144

Readme

Boilerplate

Fast, generic, simple access control system for node.js.

Installation

$ npm install nod

Quick start

nod is used by consuming applications to manage a map of permissions that let you later check or enforce that certain subjects have permissions on specific objects. It does not try and enforce a particular storage paradigm on your application, nor does it presume anything about the hierarchy of your stuff. You simply grant, revoke, check, or enforce as appropriate.

#grant# grant(, , )

var nod = require('nod');

// assuming some object named article
nod.grant('peter', article.id, 'read');

At this point, nod's permissions map will record that the subject identified as 'peter' will have the permission to 'read' the article. Note that all the parameters are pretty arbitrary; nod attaches no semantic meaning to your permission names, nor does it assume any kind of inheritance in this release. You can, however, check peter's rights as follows:

nod.check('peter', article.id, 'read'); // returns true
nod.check('peter', article.id, 'write'); // returns false
nod.enforce('peter', article.id', write'); // throws an AccessDeniedError

If you later change your mind, you can always revoke permissions as well

nod.revoke('peter', article.id, 'read');

You can also view a copy of the permissions map through getPermissions

nod.grant('peter', '102029192', 'read');
nod.getPermissions();
// returns { '102029192' : { permissions : { read : ['peter'] }}}

And finally, you can set permissions as well

nod.setPermissions({'102029192' : { permissions : {read : ['peter','stewie']}}});
nod.check('stewie', '102029192', 'read'); // returns true