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

fnforge

v0.0.1

Published

A universal standard for functions with bidirectional communication support.

Readme

fnforge

Note: This project is a Work in Progress (WIP).

fnforge is a new, universal standard for functions. It aims to provide a consistent way to define, discover, and execute functions across different platforms and programming languages.

The Problem

Traditionally, functions are exposed and consumed in various ways:

  • CLI: Arguments and flags, often string-based and parsed manually.
  • REST: JSON payloads, headers, and query parameters, with varied schemas.
  • Programming Languages: Language-specific types, interfaces, and calling conventions.

Each of these methods defines inputs and outputs differently, leading to fragmentation and the need for constant translation between formats.

The Standard

fnforge introduces a unified approach. In this standard, every function must explicitly define:

  • The type of input (In)
  • The type of output (Out)

The format also specifies bidirectional communication, allowing for interactive or streaming exchanges between the caller and the function.

Notably, fnforge focuses on the communication contract and data structures without necessarily specifying the transport data layer. This allows the standard to be implemented over various protocols (like WebSockets, gRPC, HTTP/3, or even local pipes) while maintaining a consistent functional interface.