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

looksfake

v1.0.1

Published

Tiny CLI to create synthetic API keys

Readme

looksfake GitHub Actions Workflow Status

Zero-dependency CLI that creates a synthetic API key in the same shape as a real one.

  • Example:

    npx looksfake 418937625:AAHk-9BwNp4TzXc7Jm_VrQ2FyDs8LgUeM1P

    Output:

    123456789:ABCd-0EfGh1IjKl2Mn_OpQ3RsTu4VwXyZ5A

Why not?

You should not trust npm packages, you should never paste a real API key in a tool you haven't read end to end. There are several layers where it could become malicious:

  • An npm package can have different content from GitHub repository. This repository does use GitHub Actions to guarantee the same, but it guards the author more than the users. Nothing stops the attacker from replacing the npm package later.

  • Even if the content is the same as on GitHub, a package can hide malicious content inside a dependency. Although, this package is zero-dependency.

  • If you read the source code on GitHub, the malicious code could be hidden after whitespace, because sometimes it's hard to spot the horizontal scrollbar.

  • The API key is going to land in your shell history.

If that didn't stop you, consider changing a few letters before running the script. Replacing three characters in a 38 characters long key would already require an attacker to test ~150 million combinations.

License

Apache-2.0