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

apifae

v0.6.0

Published

Mock HTTP APIs locally and keep the mocks honest as the API changes

Downloads

738

Readme

apifae

APIFae mocks the HTTP APIs your code depends on, and tells you when those mocks stop matching the real API.

A mock is written once, but the API it stands in for keeps changing. Tests that use the mock go on passing against responses the API no longer sends. APIFae is built to catch that:

  • apifae init reads an OpenAPI 3.x or Swagger spec and writes one mock per documented path, as YAML files you commit. apifae record can build them from a real API's traffic instead.
  • apifae up serves the mocks on your machine or in CI. Edit a mock and the next request reflects it.
  • apifae diff <url> compares each mock with the live API. It exits 1 when a mock has drifted and 2 when it can't reach the API, so a CI job can tell drift from an outage. It needs no spec; given one, it also checks the API against it.
  • apifae patch <url> writes what diff found back into your mocks.

APIFae is a single native binary, so there is no runtime to install first. The CLI is free and will stay free.

Install

npx apifae --version          # try it without installing
npm install --global apifae   # or keep it

This package has no binary of its own. It lists five platform packages as optional dependencies (@apifae/darwin-arm64, @apifae/darwin-x64, @apifae/linux-arm64, @apifae/linux-x64 and @apifae/win32-x64), and npm installs the one that matches your machine. Nothing is downloaded after install and there is no install script, so npm install --ignore-scripts works too.

Learn more

Guides, the command reference and the other ways to install (Homebrew, Scoop and a shell script) are at https://apifae.com.

Closed source; binaries under MIT or Apache-2.0.