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

httpexec

v0.0.2

Published

Run local commands over HTTP, described by OpenAPI. Executes directly — there is no shell unless you ask for one.

Readme

httpexec

Runs local commands over HTTP and describes itself with OpenAPI, so an API client — or an Arazzo workflow — can shell out without leaving the description.

There is no shell

Commands are executed directly, not interpreted. Shell syntax — redirection, pipes, globs, &&, variable expansion — is passed through as literal text:

{ "command": "echo", "args": ["hello > world.txt"] }
// → { "stdout": "hello > world.txt\n", "exitCode": 0 }, and no file

Ask for a shell when you want one:

{ "command": "sh", "args": ["-c", "echo hello > world.txt"] }
// → { "stdout": "", "exitCode": 0 }, and the file exists

Pass untrusted values as arguments rather than splicing them into the command, so they cannot escape it:

{ "command": "sh", "args": ["-c", "printf %s \"$1\" > out", "sh", "«value»"] }

Security

This server runs whatever it is told to run, and has no authentication. Anything that can reach the port has the privileges of the user running it.

It binds localhost on a random port by default. Do not change that unless you have put authentication in front of it. --hostname 0.0.0.0 publishes remote code execution to your network.

Usage

npx httpexec --port 8080

| Flag | Default | | | --- | --- | --- | | --port, -p | 0 | 0 picks a free port. | | --hostname, -h | localhost | See above before changing. |

curl -X POST http://localhost:8080/ \
  -H 'content-type: application/json' \
  -d '{"command":"echo","args":["hello"]}'
{ "stdout": "hello\n", "stderr": "", "exitCode": 0 }

The OpenAPI description is served from /openapi.json, with servers set to the address it is actually reachable at.

A command that fails is still a 200

The response reports what happened; it is not itself the verdict. A command that ran and exited non-zero returns 200 with that exitCode. Only a malformed request body is a 400.

So check exitCode, not just the status:

successCriteria:
  - condition: $statusCode == 200
  - condition: $response.body#/exitCode == 0

Requirements

Node 22.18 or newer — the binary is TypeScript, run through Node's built-in type stripping.

License

MIT