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

@thooto/role-acl

v4.5.1

Published

Role, Attribute and Condition based Access Control for Node.js

Downloads

9

Readme

Role ACL

This library is an extension of role-acl.

Added features

  • Use JSON Path to compare a key with another in the condition arguments.
  • Support for undefined (or any boolean-negative value) argument value in the condition.
  • Provide a parameter on permission filter to interprete the data as a Sequelize query.

Guide

import { AccessControl } from "@thooto/role-acl";

const ac = new AccessControl();

JSON path

// Assuming:
// Video.hasMany(Review);
// Review.belongsTo(Video);

ac.grant("user")
  .action("read")
  .condition({
    Fn: "EQUALS",
    args: {
      '$.query.include[?(@.model=="User")].where.id': "$.issuer.id", // Restrict to user's own videos
      "$.query.where": undefined // Forbid where parameter
    }
  })
  .on("video");

const req = {
  query: {
    attributes: ["url", "size"],
    include: [{ model: "User", where: { id: 2 } }]
  },
  issuer: {
    id: 2
  }
};

const permission = ac
  .can("user")
  .context(req)
  .execute("read")
  .sync()
  .on("video");
// Should not throw

Video.findAll(req.query);

Query attributes filter

// Assuming Video and Review are Sequelize models:
// Video.hasMany(Review);
// Review.belongsTo(Video);

ac.grant("user")
  .action("read")
  .on("video", ["url", "Review.commentary"]);

const permission = ac
  .can("user")
  .execute("read")
  .sync()
  .on("video");

const query = {
  attributes: ["url", "size"],
  include: [{ model: "Review", attributes: ["commentary", "mark"] }]
};

permission.filter(query, { query: true });
// Query now is:
// { attributes: ["url"], include: [{ model: "Video", attributes: ["mark"] }] }

Video.findAll(query);

To do

  • Add JSON Path usage to all context functions (currently only Fn: "EQUALS").

Licenses