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

@polymerix-labs/dont-break-query

v0.4.0

Published

JSON CLI over the dont-break structural query API, for shell scripts and CI pipelines

Readme

@polymerix-labs/dont-break-query

JSON CLI over the dont-break structural query API, for shell scripts and CI pipelines. Results are printed as raw JSON on stdout so they compose with jq.

npx @polymerix-labs/dont-break-query arch-status

Setup

Set four environment variables (the dont-break extension's Connect your agent panel provides ready-to-copy values):

export DONT_BREAK_API_URL="https://api.dont-break.dev"
export DONT_BREAK_TOKEN="<jwt>"
export DONT_BREAK_WORKSPACE="<workspace-id>"
export DONT_BREAK_PROJECT="<project-slug>"

Configuration is environment-only by design: tokens never appear in argv, process lists, or shell history.

Commands

| Command | Purpose | |---------|---------| | find <name> [--kind <kind>] [--limit <n>] | Resolve a name/path into graph nodes (entry point — other commands take node ids) | | dependencies <node_id> [--depth <n>] | What a node depends on | | dependents <node_id> [--depth <n>] | Who depends on a node | | impact [--file <path>]... [--node <id>]... | Blast radius of a change | | path <from> <to> [--k <n>] | Cheapest dependency routes between two nodes | | do-not-touch [--scope <prefix>] | Danger list: high fan-in + low stability | | arch-status | Practicability report + verdict | | check [--file] [--node] [--diff] [--allow-warn] | Team rules vs a planned change (exit 1 on warn, 2 on block) | | propose-rule --kind --name --severity | Propose a rule (warn active now; block waits for a human) | | pause-own-rule <rule_id> | Pause a rule this agent token authored | | append-rule-reason <rule_id> <text> | Append one reason to any rule (add-only) |

Exit codes

| Code | Meaning | |------|---------| | 0 | Success (JSON result on stdout). check: verdict ok | | 1 | API or network error (JSON { error, code, status } on stderr). check: verdict warn | | 2 | Usage or configuration error (JSON { error } on stderr). check: verdict block |

check --allow-warn keeps a warn verdict at exit 0 so a pipeline can fail only on block.

Examples

# Gate a CI job on architectural health
verdict=$(dont-break-query arch-status | jq -r .practicability.verdict)
[ "$verdict" != "critical" ] || { echo "architecture critical — blocking merge"; exit 1; }

# Files changed in this merge request
git diff --name-only origin/main... | dont-break-query check --diff -

# Refuse to touch danger-zone files
dont-break-query do-not-touch --scope src/services | jq -e 'length == 0'

All business logic (weights, caps, thresholds) lives server-side; the CLI is a pure transport built on @polymerix-labs/agents-core.

License

MIT