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

permissions-policy-parse

v0.1.0

Published

Zero-dependency Node.js parser for the HTTP Permissions-Policy / Feature-Policy headers with typed allowlist extraction and validation

Downloads

18

Readme

permissions-policy-parse

Zero-dependency Node.js parser for the HTTP Permissions-Policy and Feature-Policy response headers.

Parses header values like camera=(); microphone=(self "https://trusted.example.com"); geolocation=(self) into typed JavaScript objects, with a serializer, per-feature allowlist extractor, and isFeatureAllowed predicate.

Install

npm install permissions-policy-parse

API

import {
  parsePermissionsPolicy,
  serializePermissionsPolicy,
  getFeatureAllowlist,
  isFeatureAllowed,
  PermissionsPolicyParseError,
} from 'permissions-policy-parse';

parsePermissionsPolicy(headerValue, options?)

Parses a header value and returns an object with directives array and the raw string.

const result = parsePermissionsPolicy(
  'camera=(); microphone=(self "https://trusted.example.com"); geolocation=(self)'
);
// → {
//     directives: [
//       { feature: 'camera', allowlist: [] },
//       { feature: 'microphone', allowlist: [
//         { type: 'self' },
//         { type: 'origin', value: 'https://trusted.example.com' }
//       ]},
//       { feature: 'geolocation', allowlist: [{ type: 'self' }] }
//     ],
//     raw: 'camera=(); microphone=(self "https://trusted.example.com"); geolocation=(self)'
//   }

Options:

  • allowUnknownFeatures (default false) — set true to accept feature names not in the W3C registry
  • normalize (default true) — set false to preserve the raw field exactly as given

serializePermissionsPolicy(obj)

Round-trip a directives object back to a header string.

serializePermissionsPolicy({
  directives: [
    { feature: 'camera', allowlist: [] },
    { feature: 'geolocation', allowlist: [{ type: 'self' }] }
  ]
});
// → "camera=(); geolocation=('self')"

getFeatureAllowlist(feature, headerValue)

Extract the allowlist for a specific feature.

getFeatureAllowlist('microphone', 'camera=(); microphone=(self "https://example.com")');
// → [{ type: 'self' }, { type: 'origin', value: 'https://example.com' }]

isFeatureAllowed(feature, originOrKeyword, headerValue)

Check whether a keyword ('self', 'src', 'none', '*') or origin is in the allowlist for a feature.

isFeatureAllowed('geolocation', 'self', 'geolocation=(self)');
// → true

isFeatureAllowed('camera', 'https://evil.com', 'camera=("https://example.com")');
// → false

PermissionsPolicyParseError

Thrown on malformed input. Has message, input, and position properties.

Feature-Policy Compatibility

Both Permissions-Policy (W3C, 2020–present) and its predecessor Feature-Policy (2018–2020) use identical syntax. This library parses both:

parsePermissionsPolicy('camera=self; microphone=none');
// Works — Feature-Policy bare keyword form

Syntax

Permissions-Policy = Directive *( ';' Directive )
Directive = feature-token '=' ( '*' | allowlist )
allowlist = '(' *( token / quoted-origin ) ')'
token = 'self' | 'none' | 'src' | 'lazyload' | 'lazyload-allowlist'
quoted-origin = '"' uri '"' | "'" uri "'"

Key rules:

  • No space between feature name and =
  • Origins must be quoted (double or single quotes)
  • camera=* means "allowed in all contexts"
  • camera=(none) or camera=() means "fully blocked"
  • 'self' is a keyword token, not the literal string "self"

Test count

100 tests (run with npm test).

License

MIT