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 🙏

© 2026 – Pkg Stats / Ryan Hefner

react-simple-access-engine

v0.1.0

Published

Simple provider-based access control primitives for React.

Readme

react-simple-access-engine

Provider-based access control primitives for React.

Install

npm install react-simple-access-engine

What it provides

  • AbacProvider to inject permissions once at the app boundary
  • useAbac(feature, action) for function-style access checks
  • AbacFunction render-prop wrapper for flexible branching
  • AbacComponent for component-level guards
  • AbacPage for page-level guards with a default forbidden fallback

Permission shape

The engine expects permissions in the shape below:

{
  billing: ["view", "pay", "export"],
  workspace: ["create", "view"],
}

Feature and action matching is case-insensitive.

Wildcard access is supported:

  • billing: ["*"] grants every action under billing
  • * : ["*"] grants every action across every feature

Match precedence:

  1. exact feature + action
  2. feature + "*"
  3. "*" + "*"

Basic usage

import {
  AbacProvider,
  AbacComponent,
  AbacPage,
  AbacFunction,
  useAbac,
} from "react-simple-access-engine";

const permissions = {
  billing: ["view", "pay", "export"],
  workspace: ["create", "view"],
};

export const App = () => (
  <AbacProvider permissions={permissions}>
    <AbacPage feature="billing" action="view">
      <BillingPage />
    </AbacPage>
  </AbacProvider>
);

API

AbacProvider

Wrap your app once and pass the permissions object:

<AbacProvider permissions={permissions}>
  <App />
</AbacProvider>

If permissions is undefined, access is treated as not ready yet.

useAbac(feature, action)

Returns:

{
  canAccess: boolean;
  isReady: boolean;
}

AbacFunction

Render-prop wrapper:

<AbacFunction feature="billing" action="view">
  {({ canAccess, isReady }) =>
    isReady && canAccess ? <BillingPanel /> : <EmptyState />
  }
</AbacFunction>

AbacComponent

Component wrapper:

<AbacComponent feature="billing" action="view">
  <BillingPanel />
</AbacComponent>

Optional props:

  • fallback: rendered when access is denied
  • loadingFallback: rendered while permissions are unresolved

AbacPage

Page wrapper:

<AbacPage feature="billing" action="view">
  <BillingPage />
</AbacPage>

If access is denied, it renders a forbidden page by default. You can override that with fallback.

Notes

  • The package does not depend on Redux.
  • The package does not require React Router.
  • Keep permissions normalized in one place, ideally at your app boundary.