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

sonarqube_prep

v0.1.4

Published

A CLI tool to prepare SonarQube projects.

Readme

sonarqube_prep

Branches Functions Lines Statements Test coverage

SonarQube_prep is a helper application meant to make it easier to prepare projects, that are provisioned in SonarQube already, to have the needed files and information to show information. It will not provision a project in SonarQube for you. This should be done with more control from the UI itself.

Running

npx sonarqube_prep

On a first run, you will be asked to provide a url for your sonarqube instance and a token. The URL must be provided, the token is optional. This information will be stored locally only in ~/.sonarqube_prep

Questions asked:

  • provide the default branch name (default is collected but can be overriden)
  • provide the Project Key (must match the project key in SonarQube)
  • provide the token for the badges (must match the token as seen in the project info in SonarQube)
  • select the badges you want to add to the README.md
  • Confirm if you would like to create a GHA for SonarQube

Demo


Output

As a result, the README.md file will have the badges selected added to the top of the file. A sonar-project.properties will be created, along with a .github/workflows/sonarqube-build.yml if opted in. Not wanting the GHA will show a short snippet that can be used in a different action yml file.

Manually left to do:

The sonar-project.properties will only contain the project_key, nothing else. You will stil have to set exceptions, inclusions, or exclusion if you wish to do so, specify python versions, or the location of a coverage.xml file.

Why

I found it troublesome and error prone to setup multiple repositories and always having to remember where what information comes from. When supplying the token it really speeds things up by getting all the needed information for you.

local development

npm install

To run:

npm run lib/index.ts

build

npm run build

publish

npm run publish