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-posthog

v1.0.2

Published

PostHog Protocol 3 twin: every spec operation answers the vendor-shaped gap; detected integrations require opt-in.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

volter-oliveriovolter-oliverioaaronvolteraaronvolter

Keywords

twinposthoganalyticshogql

Readme

@volter/twin-posthog

Protocol 3 twin of PostHog's API and public ingestion endpoints. Nothing is served: every spec operation answers the vendor's unknown-request response. The API answers 404 with {"type":"invalid_request","code":"not_found","detail":"Endpoint not found.","attr":null} (the pinned server's api_not_found and exceptions-hog envelope). Ingestion answers an empty 404, the pinned capture server's Axum default. The manifests cite those sources.

Cal.com, Postiz and Rallly require opt-in configuration absent from their shipped defaults. journeys/demand.json records their scanned commits, gates and file:line call sites. There are no resources, credential doors, screens, handlers or refresh; the required kernel discovery and clock doors remain. The customer life has no acts.

The vendored specs, provenance, hashes and published examples are retained under api/spec and ingest/spec. Examples of unmodeled operations are counted as unserved; they do not expand the pack's scope.