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

@volter/twin-perplexity

v1.0.0

Published

Perplexity Protocol 3 API twin: every spec operation answers the vendor-shaped gap; no scanned application calls Perplexity.

Readme

@volter/twin-perplexity

Protocol 3 twin of the Perplexity AI API. Nothing is served: neither demand record names Perplexity among the 18 scanned applications, and no platform or other-pack runtime caller adds an operation. Every spec operation is unmodeled, including the documented legacy chat-path correction. There are no handlers, resources, credential doors, model scenarios or refresh. The kernel retains its standard discovery and World doors.

Unserved operations and unknown paths answer the documented unknown-resource 404 class in the vendor's JSON error.message envelope. The documentation does not fix literal URL-refusal text, type or code; the gap says Not found without inventing a code. Bearer authentication and the 401 class remain declared from the vendor's documentation.

The life is empty. Published spec examples are unchanged and counted as examples of unserved operations. spec/SOURCE.md records the unchanged upstream document, its correction, provenance, version and hashes.