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

@responsive-privacy/core

v0.1.1

Published

Core privacy transformation engine — framework-agnostic attribute filtering based on the Superbloom/Draftlab Attribution Taxonomy

Readme

@responsive-privacy/core

Framework-agnostic build-time PII protection engine. Filters, redacts, or omits content fields based on a 5-level privacy taxonomy derived from the Superbloom/Draftlab Responsive Transparency research.

Part of the Responsive Privacy monorepo.

Install

pnpm add @responsive-privacy/core

Usage

import { defineConfig, createContext, transformEntry } from '@responsive-privacy/core';

const config = defineConfig({
  collections: {
    team: {
      fields: {
        name:       'ID-01',  // Full Name — visible at Level 2+
        role:       'ID-03',  // Job Title — visible at Level 1+
        email:      'CV-01',  // Email — visible at Level 4 only
        department: 'OR-01',  // Department — visible at Level 1+
      },
    },
  },
});

// Create context for the current build (reads PRIVACY_LEVEL env var)
const ctx = createContext(config);

// Transform a content entry
const result = transformEntry('team', {
  name: 'Jane Smith',
  role: 'Program Director',
  email: '[email protected]',
  department: 'Programs',
}, ctx);

// At PRIVACY_LEVEL=1:
// result.data.name → "Staff Member" (replaced)
// result.data.role → "Program Director" (visible)
// result.data.email → "Contact the organization" (replaced)
// result.data.department → "Programs" (visible)

API

Configuration

  • defineConfig(config) — define a privacy configuration with collection field mappings
  • resolveConfig(config) — merge user config with the default 20-attribute taxonomy
  • readPrivacyLevel(fallback?) — read PRIVACY_LEVEL from env (0–4, defaults to 4)
  • createContext(config, level?) — create a resolved privacy context for a build

Transformer

  • transformEntry(collectionName, data, ctx) — transform a single entry's fields based on privacy level
  • transformCollection(collectionName, entries, ctx) — transform an array of entries
  • isAttributeVisible(attributeId, level, attributes) — check if an attribute is visible at a given level
  • getRedactedValue(attr) — get the replacement value for a hidden attribute
  • buildSummary(results, ctx) — generate a build log showing what was hidden

Defaults

The full 20-attribute taxonomy ships as defaults and can be imported separately:

import { DEFAULT_ATTRIBUTES, DEFAULT_PRIVACY_LEVELS } from '@responsive-privacy/core/defaults';

Privacy Levels

| Level | Name | What's Visible | |-------|------|----------------| | 0 | Complete Anonymity | Nothing — all PII hidden | | 1 | Role-Only Visibility | Job titles and departments only | | 2 | Professional Identity | Names, roles, project attribution | | 3 | Public Professional | Full professional profile, no contact info | | 4 | Full Transparency | Everything including contact details |

License

MIT