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

@phyi/cli

v0.2.1

Published

Verify a package before you install it, and gate a build on the verdict.

Readme

@phyi/cli

npm

Verify a package before you install it, and gate a build on the verdict.

The CLI answers one question at the point where it still matters: is this safe to add? It runs on your machine before you commit, not after CI rejects the branch, and its exit code carries the verdict so a pipeline needs nothing else to make a pass or fail decision.

Install

npm install -g @phyi/cli

Or run it without installing:

npx @phyi/cli verify npm/[email protected]

Authenticate

Verification needs a paid plan. Create a token at app.phyi.dev, then:

phylax auth login

The token is written to ~/.config/phylax/config.json with owner-only permissions. PHYLAX_API_TOKEN overrides it, which is what CI should use.

Verify one package

phylax verify npm/[email protected]
phylax verify pkg:pypi/[email protected]

Both spellings work. A bare name is refused rather than guessed at, because express exists on more than one registry.

Verify a whole project

phylax repo .

Reads every lockfile it finds and verifies what they install.

Exit codes

| Code | Meaning | | --- | --- | | 0 | ALLOW, or WARN without --strict | | 1 | BLOCK | | 2 | WARN under --strict | | 3 | Could not resolve, no token, or the plan does not cover it |

WARN passes by default on purpose. New findings land against dependencies you did not change, so a pipeline that fails on every warning fails on quiet days and gets switched off. Add --strict once your baseline is clean.

Flags

| Flag | Effect | | --- | --- | | --json | Machine readable output | | --strict | Treat WARN as a failure | | --fail-on <verdict> | Set the verdict that fails the command | | --debug | Verbose diagnostics |

Layout

src/commands/   verify, repo, auth
src/lib/        argument parsing, config, exit codes, references, output
test/unit/      unit tests

The rest of Phylax

| Tool | Where to get it | | --- | --- | | JavaScript SDK | @phyi/sdk on npm | | MCP server | @phyi/mcp on npm | | Agent runtime gate | @phyi/runtime-gate on npm | | VS Code extension | phylax.phylax on the Marketplace | | GitHub Action | praxi-labs/phylax-action |

Docs live at phyi.dev.