npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details


  • User packages



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.


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 🙏

© 2021 – Pkg Stats / Ryan Hefner




This is simply a CDK wrapper for the SAM/SAR application - [aws-lambda-power-tuning](




CDK Lambda Power Tuner

This is simply a CDK wrapper for the SAM/SAR application - aws-lambda-power-tuning

Note this is an alpha module, it needs thoroughly tested before being production recommended

All of the lambda logic is cloned on build from that source repo with only the stepfunction definition being defined in this project.

This enables you to now do this:


Deploying the state machine

Import it into any CDK stack and then cdk deploy

Running The Tuner

This is the same as here

Differences from aws-lambda-power-tuning

Since this uses AWS CDK to build and deploy the step function, we need to play by the rules of CDK.

The method of integrating Lambda functions as a step into your workflow via ARN has been deprecated by the team. They have chosen to support integrating via function name. For reference see issue

This means that the payloads coming back from the Lambda functions contain an extra abstraction layer of data not present in the SAR application.

To make this work without rewriting the Lambda functions so that I can always pull the latest code on every build I had to introduce adapters between the step function Lambda tasks to strip out this abstraction layer. This is their only purpose

stepfunction flow