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

@workingmodel/who-changed-this

v1.0.0

Published

Git blame but useful — tells you why a line changed, not just who changed it.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

working-modelworking-model

Keywords

gitblamehistorycommitprpull-requestticketjiralineardebugcliwhy

Readme

@workingmodel/who-changed-this

Git blame but useful — tells you why a line changed, not just who changed it. Developed by Working Model.

npm version npm downloads license

who-changed-this src/auth.ts 42

Line 42 of src/auth.ts last changed in:

  Commit:  a3f8c12  3 weeks ago
  Author:  Jane Smith <[email protected]>
  Date:    2026-05-18
  Message: fix: skip token refresh when session is already expired
            Previously we'd attempt a refresh even on fully expired sessions,
            causing a retry loop. Now we bail early and redirect to login.

  Branch:  fix/auth-token-refresh
  Merged:  Merge pull request #312 from fix/auth-token-refresh (b9e1d44)

  Tickets:
    ENG-847 → https://linear.app/...
    #312 → https://github.com/org/repo/issues/312

  PR:      #312 Fix auth token refresh loop on expired sessions
            https://github.com/org/repo/pull/312

  Related commits (3):
    a3f8c12 fix: skip token refresh when session is already expired
    d4e9b01 refactor: move token validation to separate function
    c2a7f55 test: add coverage for expired session edge case

Install

npx @workingmodel/who-changed-this <file> <line>

Or install globally:

npm install -g @workingmodel/who-changed-this

Usage

who-changed-this src/auth.ts 42
who-changed-this src/auth.ts:42

Must be run from inside a git repository.

What It Shows

| Info | Source | |------|--------| | Commit SHA, author, date, message | git blame + git show | | Branch the change came from | git branch --contains | | Related commits in the same branch/PR | git log ancestry path to merge commit | | Ticket references | Extracted from commit message, body, and branch name — supports Jira (PROJ-123), Linear (ENG-456), and GitHub (#789) | | PR title, description, URL | gh CLI if installed and authenticated (graceful fallback if not) |

Why This Exists

git blame tells you the commit SHA and the author's name. It doesn't tell you why. You then go to git log, find the commit, read the message, wonder if there's a PR, open GitHub, search for the SHA, find the PR, read the description, notice there's a Jira ticket, open Jira. That's six steps for one question.

This does all six steps in one command.

More tools from Working Model → workingmodel.co · npm @workingmodel