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

create-effing

v0.1.0

Published

Defensive placeholder — use `npm create @effing` (with the @ scope) to scaffold an Effing project.

Readme

create-effing

This is a placeholder package. It exists so the unscoped create-effing name on npm cannot be hijacked by a third party to attack users who typo the official command.

You probably want this instead

npm create @effing my-app
pnpm create @effing my-app
yarn create @effing my-app

These resolve to @effing/create, the real Effing project scaffolder.

If you accidentally ran npm create effing (without the @), this package will print the correct command and exit with a non-zero status. It never downloads, executes, or generates anything on your machine.

Why this exists

npm create <name> resolves to the unscoped package create-<name>, while npm create @scope resolves to @scope/create. Those are different packages on the registry. Publishing a benign placeholder on the unscoped name closes a typosquatting hole that could otherwise be used to run arbitrary code during scaffolding.

See @effing/create for the actual scaffolder source.