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

v1.0.0

Published

Deepgram Protocol 3 twin: every spec operation answers the vendor-shaped gap; Postiz clipping requires opt-in.

Readme

@volter/twin-deepgram

Protocol 3 twin of Deepgram's REST API. Nothing is served: every spec operation answers the vendor-shaped gap. No transcription, scenario adapter, credential door, stored resource or refresh is served.

Postiz clipping requires STORAGE_PROVIDER=cloudflare, selecting cloud storage over its shipped local provider. RunPod endpoints and client credentials authorize processing after that storage choice. The pinned configuration and optional call are recorded in journeys/demand.json; the customer life has no steps.

Authentication retains the documented Token and Bearer forms. Missing or malformed credentials receive 401 INVALID_AUTH. The docs give no unknown-route body, so the gap uses their documented 404 PROJECT_NOT_FOUND class with err_code, err_msg and request_id (errors). No vendor key is issued or stored.

spec/SOURCE.md records the unchanged vendored spec and its hash. Published examples remain unchanged and count as unserved; every operation's reason is in journeys/decisions.json.