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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@iarna/git-ll

v1.1.1

Published

git log with npm git repo metadata

Downloads

4

Readme

git-ll

Git commit log, pulling out commit info in the format that the npm cli project uses.

Usage

$ npx @iarna/git-ll

or

$ npm install -g @iarna/git-ll
$ git ll

Output

Output looks like this:

example output, see text version below

637f2548f^#17748 [#17637] finalize: When rolling back use symlink project-relative path (#17748) (@iarna on 2017-07-12 ↑@zkat)
  • 637f2548f - Is the first nine characters of the commit hash, this is the git "short form".
  • ^ - If there's a carrot here it means this commit has been peer reviewed (that is, its description has a Reviewed-By).
  • #17748 - If PR-URL is in the description then this is the PR#. If there's more than one then this will be a comma separated list.
  • [#17637] - If Fixes is in the description then this is the issue #. If there's more than one then this will be a comma separated list.
  • finalize: When rolling back use symlink project-relative path (#17748) - The subject, that is, the first line of the raw commit message.
  • @iarna - If Credit is in the description then this is a comma separated list of those values. If not, this is the Author Name from git.
  • 2017-07-12 - The UTC date this was committed.
  • ↑@zkat - If Reviewed-By is in the description then its value will be here.