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

gettodaysdate

v1.0.62

Published

Return a fixed ISO date.

Readme

gettodaysdate

npm version npm downloads license published by puppeteer + a custom passkey

Returns a fixed ISO date.

const { getTodaysDate } = require('gettodaysdate');

getTodaysDate(); // '2026-10-25'

Why?

This is a PoC and a middle finger to NPM's change to force passkeys for publishing on everyone, because they think their users are too dumb.

Sure, there have been supply chain attacks, yeah tokens got leaked, whatever. That's the users fault. I mean you guys already blocked scripts and git etc. by default on npm 12, but forcing either passkeys or OIDC on a few providers is dumb.

Well, I will use my own passkeys, via keys I generate with OpenSSL! And guess what, since I can set the credentialId to any 32 bytes I want, I will have some fun with it:

How?

Review the SETUP.md doc on how to register a custom passkey via a shim, and the release folder for how the publishing works via puppeteer + custom passkeys

AI Use

This was primarily done via some human webauthn research, and then prompting an LLM to help write shims, docs and the rest.

License

WTFPL