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

@atlasauth/pca-policy-ci

v0.4.1

Published

CI gate for PCA policies: statically flag over-broad grants, privilege-escalation in delegation chains, unused/redundant caveats, and reachability of dangerous actions — fail the build before an unsafe policy ships.

Readme

@atlasauth/pca-policy-ci

A CI gate for Proof-Carrying Authority (PCA) policies. It statically analyzes an envelope, a minted grant, or a delegation chain and reports findings so an unsafe policy fails the build before it ships. It is driven by the @atlasauth/pca-analyzer decision procedure.

Rules (each can be toggled):

  • over-broad-grant: wildcard verb or resource, a provable always-allow, or a dangerous verb with no narrowing condition
  • privilege-escalation: a delegation hop whose authority is not a subset of its parent
  • redundant-caveat: a duplicate, subsumed, unsatisfiable, or non-binding caveat or condition
  • dangerous-reachability: a dangerous action provably reachable with no budget, rate, or step-up gate
  • missing-safety-floor: no expiry, or no blast-radius, rate, or budget gate on a non-trivial grant

A hard error is only emitted from a proven analyzer verdict; undecidable features (regex resources, cross-field refs, over-large grids) degrade to a warn or info that says so.

Install

npm i -D @atlasauth/pca-policy-ci

Usage

CLI:

npx pca-policy-ci policies/*.json [--max-severity error|warn|info] [--format text|github] [--quiet]

Each file is a JSON envelope, grant, compiled policy, { predicates, caveats }, or an array (treated as a delegation chain). The exit code is non-zero when any finding reaches --max-severity (default error). --format github emits GitHub Actions annotations.

Library:

import { lint, lintPolicies } from '@atlasauth/pca-policy-ci';

const findings = lint({
  predicates: [{ verb: '*', resource: '*' }],
  caveats: [],
});
// [{ rule: 'over-broad-grant', severity: 'error', message: '...', where: 'predicates[0]' }, ...]

const summary = lintPolicies(
  [{ label: 'refund-agent', policy: envelope }],
  { maxSeverity: 'warn' },
);
process.exit(summary.exitCode);

API

  • lint(input, opts?): dispatches to lintPolicy (single policy) or lintChain (array)
  • lintPolicies(items, opts?): labeled batch, returns a LintSummary with counts, ok, exitCode
  • summarize(results, opts?), normalizePolicyInput, DEFAULT_DANGEROUS_VERBS
  • Options: rules to enable/disable or tune each check (dangerous verbs, targets, safety floor)

Status

Part of Proof-Carrying Authority. A clean run means no rule fired, not that a policy is correct; it complements review, not replaces it.

License

MIT - see LICENSE