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

@setzkasten/cli

v0.5.1

Published

CI-first font license governance CLI for agencies, product teams, and enterprise compliance.

Readme

@setzkasten/cli

CLI-first tool for font license governance, audit logging, and deterministic policy/quote checks.

Positioning

  • Agencies: keep client font-license trails verifiable without slowing delivery.
  • Product teams: move license checks into CI and catch gaps during pull requests.
  • Enterprise/compliance: get deterministic evidence and audit-ready usage history at scale.

What it does (V1)

  • Initializes a project manifest (LICENSE_MANIFEST.json)
  • Writes an append-only event log (.setzkasten/events.log)
  • Adds/removes font entries
  • Imports font entries from discovered local font files
  • Scans controlled local assets for usage signals
  • Discovers likely license files and computes deterministic document_hash values
  • Links license evidence files to existing license instances (evidence add)
  • Evaluates policy decisions (allow, warn, escalate)
  • Supports policy presets: strict, startup, enterprise
  • Emits json, sarif, or junit output for scan and policy
  • Generates deterministic quote output
  • Provides dry-run/apply migration with manifest backup support

Install

npm install -g @setzkasten/cli

Usage

setzkasten init --name "My Project"
setzkasten import --path . --apply
setzkasten add --font-id inter --family "Inter" --source oss
setzkasten scan --path . --discover
setzkasten doctor --strict
setzkasten evidence suggest --path . --apply
setzkasten evidence verify --strict
setzkasten evidence add --license-id lic_inter_001 --file ./licenses/OFL.txt
setzkasten exception add --code BYO_NO_EVIDENCE --font-id inter --reason "Temporary waiver"
setzkasten report --format markdown --output compliance-report.md
setzkasten sync export
setzkasten policy
setzkasten quote
setzkasten migrate --apply
setzkasten migrate

License Evidence Workflow

Bootstrap manifest entries from discovered font files:

setzkasten import --path .
setzkasten import --path . --apply
  1. Run setzkasten scan --path . --discover to list discovered fonts and font-adjacent license files.
  2. Review result.discovered_license_files in JSON output (path, document_hash, detected_license, matched_font_ids).
  3. Optional automatic suggestions:
setzkasten evidence suggest --path .
setzkasten evidence suggest --path . --apply
  1. Link the local license file to a license instance:
setzkasten evidence add --license-id <license_id> --file <path-to-license-file>
  1. Verify evidence file paths and hash integrity:
setzkasten evidence verify
setzkasten evidence verify --strict
  1. Run setzkasten policy to verify BYO evidence state.

Policy Exceptions

Create time-bound waivers for specific policy codes:

setzkasten exception add --code BYO_NO_EVIDENCE --font-id inter --reason "Temporary waiver"
setzkasten exception list
setzkasten exception remove --exception-id <exception_id>

Reporting

Generate a governance snapshot in JSON or Markdown:

setzkasten report --format json
setzkasten report --format markdown --output compliance-report.md

Sync Snapshot

Export a stable local snapshot for dashboard/API consumers:

setzkasten sync export
setzkasten sync export --output .setzkasten/sync/project-a.json

Dependency directories such as node_modules and vendor are ignored during scans by default.

Doctor

Run environment and governance diagnostics:

setzkasten doctor
setzkasten doctor --strict

Data written locally

  • LICENSE_MANIFEST.json
  • .setzkasten/events.log

Constraints (V1)

  • No proprietary font hosting/distribution
  • No proprietary font preview
  • No general web crawling
  • Offline-first core behavior
  • Not legal advice