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

@attache/app

v0.4.0

Published

Attaché — an Envoy config workbench in the browser. Check a config, see what connects to what, and find out where a request actually goes. Run it with npx @attache/app.

Readme

@attache/app

An Envoy config workbench in a browser tab.

npx @attache/app

Opens on http://127.0.0.1:4173. Paste a bootstrap YAML or an admin /config_dump and get:

  • Findings — syntax, structure, dangling cluster references, duplicate names, two listeners on one port, routes that can never match. Each points at a line.
  • Graph — listener → filter chain → route config → virtual host → route → cluster → endpoint, with dangling references dashed and orphaned clusters flagged.
  • Route tester — a request in, and the route it takes out, with every candidate that lost at each stage and the reason it lost.

Options

-p, --port <number>   Port to listen on (default 4173, or $PORT)
    --host <address>  Address to bind (default 127.0.0.1)
    --no-open         Do not open a browser
-h, --help            Show this

Why npx and not just the website

Both exist and are the same build — the hosted copy is at https://emmettl.github.io/attache/.

But an Envoy bootstrap usually has a TLS private key a few lines below the part you wanted to ask about, and "paste your production config into a website" is a reasonable thing to refuse to do. This binds to loopback and serves a prebuilt bundle off disk using nothing but Node built-ins. There are no runtime dependencies: npx fetches one small tarball and runs, rather than resolving an install tree first.

Nothing is uploaded in either case — there is no server to upload to, and the whole analysis runs in the tab. The difference is only how much you have to take on trust.

Share links are gated on the same concern. A config in a URL fragment never reaches a server, but the link goes to a person; the app scans for key material and will not produce a link until it has been replaced with "REDACTED".

Building from a checkout

npm install
npm run dev      # Vite dev server, with the core aliased to its source
npm run build
npm start        # serve the built bundle the way npx does

The analysis lives in @attache/core, which is a plain TypeScript library with no DOM dependency if you want it without the UI.

Licence

MIT.