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

@phreshos/cli

v0.8.5

Published

The Phresh command-line interface for Program projects and system management.

Readme

@phreshos/cli

The phresh command for Program projects, runtime operations, and PhreshOS System management.

Documentation · Installation · Source

Role

The CLI presents public Project and System operations as human-facing commands. It owns command parsing, terminal output, packaging presentation, System release acquisition, and native service management.

The CLI owns its command contract. Runtime command executors use @phreshos/node and Core's shared Execute operation catalog; the CLI does not define a second System interface or transport request language.

Installation

| Package manager | Command | | --- | --- | | npm | npm install --global @phreshos/cli | | pnpm | pnpm add --global @phreshos/cli | | Bun | bun add --global @phreshos/cli | | Yarn Classic | yarn global add @phreshos/cli |

Node.js 24.15 or newer is required, as for the System it installs.

phresh create
phresh dev
phresh install
phresh system status
phresh program list
phresh execute '{"$domain":"operation","$operation":"list"}'

Use phresh describe to inspect a command, or phresh describe --all --json to read the complete machine-discoverable contract. See the CLI documentation for Program project, System, and runtime commands.

Runtime commands render direct lists or labeled fields for people by default. Add --json to receive the complete result as one JSON value for automation. phresh execute accepts and returns JSON directly.

Development

bun install --frozen-lockfile
bun run verify

verify checks the scripts, builds the CLI and bundled starter, runs the command tests, and validates the package artifact.

check performs static checks, build creates distributable output, and test runs Vitest assertions from tests/. Run build before testing built artifacts. verify runs check, build, and test in order. Operational tooling belongs in scripts/; tests and their fixtures belong in tests/. Verification uses the committed dependency graph without local package substitutions.

Related repositories

Contributing

See CONTRIBUTING.md for the repository workflow and SECURITY.md for private vulnerability reporting.

License

Licensed under the MIT License. Copyright © 2026 Zohayr SLILEH.

test:platform explicitly selects native service/installation tests for the current OS. These may change temporary host services; CI runs them on disposable runners after building.

test:live explicitly selects external-service tests. They require network access and, for providers, credentials; provider calls may incur costs.