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

thembani-github-example

v0.0.3

Published

Get a list of github user repos

Readme

package-json-to-readme Build Status

Generate a README.md from package.json contents

Installation

Download node at nodejs.org and install it, if you haven't already.

npm install package-json-to-readme --global

Usage

# Write to stdout
readme package.json

# Pipe output into a new file
readme package.json > README.md

# Add a Travis badge
readme package.json --travis

# Run tests and add their output
readme package.json --tests

# Do it all
readme package.json --tests --travis > README.md

# If your package has an example.sh or example.js file, it will be used to
# generate a usage section like this one.

# If your example.js has a require("./") statement, the relative path will be
# replaced with the package name.

Tests

npm install
npm test

> [email protected] test /Users/zeke/code/personal/package-json-to-readme
> mocha
  readme
    ✓ writes markdown to stdout (97ms)
    ✓ fails with message if package.json is invalid (95ms)
    installation
      ✓ adds --global if preferGlobal is true (86ms)
      ✓ adds --save if preferGlobal is falsy (95ms)
    usage
      ✓ injects example.js into output (88ms)
      ✓ injects example.sh into output (97ms)
      ✓ replaces relative require path with package name (89ms)
    deps
      ✓ prints out dependency metadata (96ms)
      ✓ prints out devDependency metadata (90ms)
      ✓ converts git-protocol repository URLs to https (95ms)
    --travis flag
      ✓ adds badge markdown (89ms)
      ✓ fails if repository.url is missing (94ms)
    --tests flag
      - can't easily be tested without creating an infinitely recursing test.
  12 passing (1s)
  1 pending

Dependencies

  • exec-sync: Execute shell command synchronously. Use this for migration scripts, cli programs, but not for regular server code.
  • github-url-to-object: Extract user, repo, and other interesting properties from GitHub URLs
  • hogan.js: A mustache compiler.
  • minimist: parse argument options
  • strip-ansi: Strip ANSI escape codes

Dev Dependencies

  • nixt: Simple and powerful testing for command-line apps
  • mocha: simple, flexible, fun test framework

License

MIT

Colophon