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

seneca-entity-access

v0.2.0

Published

seneca integration for entity-access

Downloads

2

Readme

seneca-perm backwards compatibility layer

The new entity-access layer provides a simpler way to resolve the same requirements that the existing seneca-perm module currently handles.

But because you might already have a configured app, it might not be feasible to re-develop the entire access control layer you have written.

This module will allow you to drive the new entity-access layer through a mostly-unmodified 'seneca-perm' options object.

Usage:

  1. Create an entities/foo/acl.js file.
  2. In this file:
var db = require('../db');

var aclSeneca = require('seneca-entity-access/perm');
var perms = require('./config/options.permissions');

module.exports = aclSeneca(db, 'foo', perms.accessControls);
  1. Load this file into the acl module in entities/foo/index.js

options.permissions changes:

  1. Go through each acl in the options.permissions file manually.

  2. You only care about records that match all of these criteria :

    • Is the entity type you care about.
    • Has 'list' amongst it's actions.
    • Has control set to 'requisite', 'required' or 'sufficient'.
  3. For each of these records, make the following changes :

    • Give the acl entry a 'lock' property with a simple identifier.
    • If the test has to be negative, add: reject: true to the object. ie: users in manual blacklist are NOT allowed.
    • If the entry uses a fn condition, you will need to reimplement it.

Re-implementing fn conditions

(see acl documentation)

TODO:

  • use s-expression like syntax for the middlepoint between other engines.
  • Support filtering of records at various places in the workflow.
  • Set of seneca actions that allow/deny requests based on new acl.