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

nafex

v2.0.3

Published

Description: Comprehensive testing library for API testing, system monitoring, and step execution tracking

Readme

⚠️ Important Notice – Temporary Issues Identified

Status: Under Active Fix 🛠️

We want to be transparent with our community.

Some issues have been identified in the current release of Nafex, and we are actively working on fixes and improvements.

What this means for users

  • Certain features may not behave as expected in specific scenarios
  • Some edge cases may cause unexpected errors or incomplete reports
  • Documentation may temporarily be ahead of the actual implementation in a few areas

What you should do

  • ✅ Use Nafex for experimentation, feedback, and non-critical testing
  • ⚠️ Avoid using the current version in production-critical environments
  • 🐛 Report any issues you encounter via the GitHub Issue Tracker

👉 Issue Tracker: https://github.com/junaidahmedshaikh/nafex/issues

What we’re doing

  • Actively fixing reported bugs
  • Aligning implementation with documented features
  • Improving stability, test coverage, and performance
  • Preparing a patched release as soon as possible

Upcoming Release

A new version will be released shortly with:

  • Bug fixes for known issues
  • Improved reliability and consistency
  • Updated documentation where needed

We truly appreciate your patience, feedback, and support while Nafex continues to evolve. 🙏 If you’ve already starred the repo, opened an issue, or shared feedback — thank you!