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

simple-code-statics

v0.1.2

Published

Simple Project code's line statistics tool

Readme

Simple Project Code Statistics

While developing in nodejs I usually need to import a lot of 3part library to make things work which not written by myself, for me it's hard to see how much code exactlly I write for the project.

when I write java in IDE like eclipse etc, I used to search '\n' globally in specified direcotries to get rough impression about scale of code line numbers, It works well in nodejs too, but it seems a little annoying and stupid to open the search-dialog to run fixed command everytime just want to know coding line nums...

So I write this tool for my tiny project, it's not perfect, not very fit industry, but useful for me.

Install

npm install simple-code-statics

Usage

  • configure the static.cfg.json
  • run command node statics.js
  • Woo get a log named like '2015-7-12_statics.log' contains each file's line num and total line num which specified in static.cfg.json file