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

fks2g

v0.5.0

Published

A CLI that estimates code change risk from git history, bug-fix commits, and GitHub issue similarity.

Downloads

710

Readme

fks2g

Since code review is the bottleneck now, fks2g helps developers decide how closely to review code.

Its for the devs who have already tried this method of reviewing code:

look how many fucks i don't give

And for devs who have realized that this code review strategy leads to a finger pointing situation when bugs or bad architecture gets shipped:

spiderman pointing

To inform how closely to review a code change, the CLI collects:

  • cosine similarity between file-name embeddings and configurable project text sources
  • an LLM judgment about whether the closest files are likely to change soon based on source documents
  • recent bug-fix commits classified by an LLM
  • file change frequency from git history
  • an LLM final risk assessment based on the collected evidence

Usage

OPENAI_API_KEY=<KEY> npx fks2g analyze --repo ../react --github-repo facebook/react --model gpt-5.5 $(git -C ../react show --name-only --format='' | tr '\n' ' ') 

This analyzes the files from the most recent commit of the react repo if you've got it cloned on your machine.

Here's a run w/ gpt 5.5:

## packages/react-server-dom-webpack/src/server/ReactFlightDOMServerNode.js:medium

Risk reason: Rare historical changes and no concrete source-document signal, but recent bug-fix activity and broad RSC relevance make changes moderately risky.
Change frequency: Rare (12 historical changes)
Recent bug fixes: b91823e: [FlightReply] Don't drop FormData entries in `decodeReplyFromBusboy` (#36468)
Source signal: not likely (RSC-related issue is a broad desired behavior, while concrete bugs target other subsystems.)
Source references: [#36491 Bug:](https://github.com/facebook/react/issues/36491), [#36430 Bug: [19.2\] DEV-build logComponentRender throws SecurityError on cross-origin Window props](https://github.com/facebook/react/issues/36430), [#36440 Bug: ReactDOM.preloadModule crashes with repeated custom as value](https://github.com/facebook/react/issues/36440), [#36497 Bug:](https://github.com/facebook/react/issues/36497), [#36379 Bug: react-refresh leaks FiberRootNodes from secondary renderers](https://github.com/facebook/react/issues/36379)

If the CLI is run against a PR in a github action environment, it'll attempt to post the anaylsis as a comment on the PR.

Docs

There's a --help flag.

Warning: 0.X software

This software is as ready for prime-time usage as its name suggests. I've only kicked the tires on it a bit with openai models. Theoretically, google, anthropic, and bedrock models are also supported.