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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@spacl/express

v1.0.0

Published

Express middleware for SPACL policies.

Readme

@spacl/express

npm version pipeline status coverage status standard-js

Express middleware for SPACL policies.

Installation

npm install @spacl/express

Documentation

API documentation is available here.

Example

First we need to create a set of policies:

# example.yml
version: 1.2
policies:
  # Create a policy describing a standard user who can
  # view other user's profiles, and edit their own.
  - name: user
    rules:
      - path: /user/+
        allow: GET
      - path: /user/:name
        allow: PUT
  # Create a derived policy describing an admin user who
  # can view, edit and delete other users' profiles, but
  # cannot delete themselves.
  - name: admin
    base: user
    rules:
      - path: /user/+
        allow:
          - PUT
          - DELETE
      - path: /user/:name
        deny: DELETE

Now we can create a basic express application that uses these policies to govern access to protected resources:

import * as express from 'express'
import { parseFileSync } from '@spacl/yaml'
import { checkPolicies } from '@spacl/express'

const app = express()
  .use(/* Your authentication middleware here. */)
  .use(checkPolicies(parseFileSync('example.yml'), {
    /* We need to know which policy to apply for this request; the authentication
       middleware above would typically be responsible for providing this. */
    getPolicy: (req, res) => req.user.policy
  }))
  /* All routes below this line are now guarded by access control policy. */
  .use('/user', /* Your route handlers here. */)
  .use(...)
  .use(...)