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

httsnap

v1.0.0

Published

A fast, local-first HTTP client for the terminal. No login, no cloud, no bloat.

Readme

apitool

A fast, local-first HTTP client for the terminal. No login. No cloud. No bloat.

Install

npx apitool GET https://api.example.com/users

Or install globally:

npm install -g apitool

Usage

apitool <METHOD> <URL> [options]
apitool run <name>
apitool list
apitool delete <name>

Examples

# Send a GET request
apitool GET https://jsonplaceholder.typicode.com/posts/1

# POST with a JSON body
apitool POST https://api.example.com/users --body '{"name":"Alice","role":"admin"}'

# Add custom headers
apitool GET https://api.example.com/me --header Authorization=Bearer\ token123

# Save a request for later
apitool POST https://api.example.com/users --body '{"name":"Alice"}' --save create-user

# Replay a saved request
apitool run create-user

# See all saved requests
apitool list

# Delete a saved request
apitool delete create-user

How saving works

Requests are saved to .apitool.json in your current directory. This means:

  • Each project can have its own saved requests
  • You can commit .apitool.json to share requests with your team
  • It's plain JSON — edit it by hand if you want

Requirements

Node.js 18 or later (uses native fetch — no dependencies).

License

MIT