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

@synmux/npm

v1.0.8

Published

Meta package for syn

Readme

@synmux/npm

Because every developer needs a metapackage that does almost nothing, but does it with style.

Metapackage for syn.

It's a package. For syn. By syn. About syn. If you were expecting more, well, that's on you.

With thanks - and apologies - to @zachleat.


Table of Contents


Why?

it is a mystery

Usage

CLI

npx @synmux/npm

Programmatic

For those who want to automate their disappointment.

First, install the package:

npm install @synmux/npm

Then you can pull it in to your heart's content:

import syn from "@synmux/npm";

syn();

Or, if you're still clinging to CommonJS:

const { default: syn } = await import("@synmux/npm");

syn();

Development

  • Written in TypeScript, because more code is more better.
  • Built and tested (no, really) with bun, because npm and yarn don't break enough.
  • Linted with biome, because someone has to care about code style.
  • For detailed codebase documentation, see AGENTS.md.

If you want to contribute, ask yourself: why?

Incoming

Believe it or not, features are planned!

  • --cv / -c parameter to dump out my CV.
  • Fetching links (and CV, when implemented) from my personal API.
    • There will always be a static fallback.
  • Literally anything useful.

Changelog

  • 1.0.1 First release! May angels rejoice.
  • 1.0.2 Minor dependency bump and twiddle to remove Node from engines.
  • 1.0.3 yanked
  • 1.0.4 yanked
  • 1.0.5 yanked
  • 1.0.6 (current) Add pronouns to the output and update Docker pins.

License

MIT.

Because you should be free to do whatever you want with this, including ignoring it entirely.

Just show me the output

Oh, alright then.

Output