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

lazygitrs

v0.0.39

Published

A faster, memory-safe, more ergonomic slopfork of lazygit

Readme

lazygitrs

A faster, memory-safe, more ergonomic slopfork of lazygit (🦀 rust btw).

This is mostly a "for me" tool — built for my own workflow. Not saying you shouldn't use it, but don't expect it to be a community project. But hey, it works for me!

Why fork? PRs were sitting too long, or the upstream direction didn't match how I wanted to work.

The goal: everything lazygit does, but faster and with opinions I actually agree with. (I can't promise backwards-compat w/ lazygit's config since it'll eventually drift w/ my own opinions, but I made sure to do that)

demo1 demo2

Install

Make sure you have:

brew install blankeos/tap/lazygitrs # Homebrew (macOS/Linux)
npm install -g lazygitrs            # or npm
bun install -g lazygitrs            # or bun
cargo binstall lazygitrs            # or cargo-binstall (prebuilt binary, faster)
cargo install lazygitrs             # or cargo (build from source)
curl -sSL https://raw.githubusercontent.com/Blankeos/lazygitrs/main/install.sh | sh # or linux/macos (via curl)

Then run:

lazygitrs

Use lazygitrs --commits to start at the checked-out HEAD commit. If filters or pagination hide HEAD, it opens a separate HEAD history view without clearing your filters. Use 2 and 4 to navigate between Files and Commits; Ctrl+G in Files generates a commit message using git.commit.generateCommand.

File tree navigation

In Files, commit/stash file lists, and compare mode, press backtick (`) to toggle the tree view. With a tree active:

  • - folds/unfolds the selected directory (including the root).
  • Enter focuses the selected file or combined directory diff without changing your normal/half/full layout; Esc returns to the file list.
  • , / . select the parent / first visible child.
  • < / > select the previous / next sibling, skipping nested descendants. Hierarchy navigation also works while the diff is focused.

These shortcuts are configurable under keybinding.universal in your config:

keybinding:
  universal:
    foldDirectory: "-"
    treeParent: ","
    treeChild: "."
    treePrevSibling: "<"
    treeNextSibling: ">"

Set a binding to "" to disable it. Collapsed directories must be unfolded before their children can be selected. Tree-navigation actions appear in ? only while a tree is active. The footer shows just the fold/unfold shortcut (default -) in tree views, not hierarchy navigation or commit details. ' (apostrophe) toggles commit details, also shown on the panel’s top-right border; explicitly remapping a tree action to ' will override it while the tree is active.

Upgrade

Detects how you installed (brew / npm / bun / cargo / install.sh) and upgrades in place:

lazygitrs upgrade          # latest
lazygitrs upgrade 0.0.32   # specific version

What's different

  • [x] AI commit messages — works with whatever agent you already use (claude, opencode, codex, or my minimal shim modelcli). Set git.commit.generateCommand (see Configuration):

    # ~/.config/lazygitrs/config.yml
    git:
      commit:
        # Using claude
        generateCommand: "claude -p 'Generate a conventional commit message for this diff. Do not hard-wrap lines; one bullet per line; blank line between paragraphs.' --no-session-persistence"
        # Using opencode
        generateCommand: "opencode run 'Generate a conventional commit message for this diff. Do not hard-wrap lines; one bullet per line; blank line between paragraphs.'"
        # Using codex
        generateCommand: "codex exec --ephemeral 'Generate a conventional commit message for this diff. Do not hard-wrap lines; one bullet per line; blank line between paragraphs.'"
        # Using modelcli
        generateCommand: 'DIFF=$(git diff --cached) && modelcli "Generate a conventional commit message for this diff. Always provide a bulletpoint body. Do not hard-wrap lines; one bullet per line. $DIFF"'
  • [x] Side-by-side + unified diffs with syntax highlighting by default and unified as well, no pager hacks needed

  • [x] Better diff navigation UX — [] new/old only views, {} for hunk traveling, hjkl←↑↓→ for line-by-line scrolling, supports mouse select/scroll too. Lots inspired by lumen

  • [x] Default GitHub conveniences — copy repo url, open repo url, copy PR create url, open PR create, copy pr url, open pr. (The 'copy' variants are useful if you use different default browsers for work/personal.)

  • [x] Branch Filtering — better experience in the Commits tab, compare what actually matters.

  • [x] Built-in compare tool — Again, inspired by lumen, but more built into the TUI. Pick a commit/branch A and a commit/branch B, then see how they differ.

  • [x] Interactive rebasing — inspired by gitlens, a clean and easy-to-use UI for pick, reword, edit, squash, fixup, drop and fast rebasing.

  • [x] Commit Details — Inspired by zed, just a small details panel about the commit that's easier to look at.

  • [x] Command Palette — easily access stuff like:

    • [x] git reset (global G) — asks which branch/commit, has quick search, then soft/mixed/hard options.
    • [x] git diff/compare (global W) and then asks what branch/commit A and B, has quick search.
    • [x] git rebase (global I) and then asks rebase on top of what branch/commit.
    • [x] 🎨 Themes + Theme-Picker!
  • [x] Grep diff contents — Ctrl-F in Files / Commit Files / Compare searches hunk lines in-context, Enter jumps to the file in the current list.

Image diffs

Selecting a PNG, JPEG, GIF (first frame), WebP, BMP, ICO, or TIFF file shows Before / After previews in Kitty and Ghostty. Added/deleted files show the available image full-width, labeled Added or Deleted. Staged previews use the index; commit-file and ref comparisons use the corresponding Git blobs.

Other binaries, unsupported/corrupt images, files over 20 MiB, and unsupported terminal environments keep the striped binary placeholder. Images are decoded with memory/dimension limits and resized in the background. SVG and video previews are not included yet.

Folder previews in the file tree mix text diffs with inline image sections. Each image section is capped at 12 rows; visible sections load in the background (two at a time) and offscreen pixels are released. This works in split/unified and wrapped views, including commit/stash folders and ref-comparison folders. Whole-commit overview buffers still retain binary placeholders. Inline images require Kitty/Ghostty placeholder graphics; other terminals keep stripes.

Set LAZYGITRS_IMAGE_PREVIEW=off to disable image previews. tmux, screen, and Zellij currently fall back to stripes. iTerm2/WezTerm and Sixel are experimental (LAZYGITRS_IMAGE_PREVIEW=experimental); their overlay cleanup is not yet fully verified. Nested editor launches avoid terminal capability queries.

Configuration

Config goes in ~/.config/lazygitrs/config.yml or ~/.config/lazygit/config.yml — both work, using either only won't break anything so you can reference the original lazygit config guide.

Persisted State lives at ~/.local/state/lazygitrs/state.yml and ~/.local/state/lazygitrs/commit_message_history you won't need to touch this.

New config properties:

  • git.commit.generateCommand — shell command for AI-generated commit messages. See What's different for examples.
  • ~/.config/lazygitrs/themes/*.json — drop custom theme files here. See Themes.

Themes

lazygitrs ships with 30+ built-in color themes (Catppuccin, Dracula, Tokyo Night, Gruvbox, Nord, etc.) sourced from OpenCode's TUI theme collection.

Unlike original lazygit, you can switch themes without touching any config file — just press ? > Color Themes > Enter. Your choice is saved automatically.

Custom themes: Drop a .json file into ~/.config/lazygitrs/themes/ and it appears in the picker. Start by copying an existing theme from src/generated_themes/ and tweaking the colors. The format is a flat JSON with all fields optional (unset values are derived from semantic base colors like primary, success, error):

{
  "id": "my-theme",
  "name": "My Custom Theme",
  "primary": "#ff6600",
  "success": "#00ff88",
  "error": "#ff3333",
  "warning": "#ffcc00",
  "text_strong": "#ffffff",
  "background": "#1a1a2e"
}

Editor integrations

Add to ~/.config/helix/config.toml — capital G keeps the built-in space g changed-file picker intact:

[keys.normal.space.G]
g = [":insert-output lazygitrs", ":redraw"]
f = [":insert-output lazygitrs -f '%{file_path_absolute}'", ":redraw"]

Absolute path matters — -f resolves it to repo-relative (e.g. apps/nextjs/next.config.ts in a monorepo).

For e (edit back in hx) — ~/.config/lazygitrs/config.yml:

os:
  editPreset: "helix"

For o (open), leave the default — OS opener (Finder for folders on macOS).

Snacks.lazygit() hardcodes lazygit, so use Snacks.terminal instead. In ~/.config/nvim/lua/plugins/snacks-lazygitrs.lua:

return {
  {
    "folke/snacks.nvim",
    opts = { lazygit = { configure = false } },
    keys = {
      { "<leader>gg", function() Snacks.terminal({ "lazygitrs" }, { cwd = LazyVim.root.git(), win = { style = "lazygit" } }) end, desc = "Lazygitrs" },
      { "<leader>gF", function() Snacks.terminal({ "lazygitrs", "-f", vim.fn.expand("%:p") }, { cwd = LazyVim.root.git(), win = { style = "lazygit" } }) end, desc = "Lazygitrs file history" },
    },
  },
}

Restart nvim (or :Lazy reload snacks.nvim) to pick it up.

For e (edit back in nvim) — ~/.config/lazygitrs/config.yml:

os:
  editPreset: "nvim"

For o (open), leave the default — it uses the OS opener (Finder for folders on macOS).

Benchmarks

Startup benchmark using hyperfine:

Benchmark 1: lazygitrs --version
  Time (mean ± σ):       4.2 ms ±   1.3 ms    [User: 1.2 ms, System: 0.9 ms]
  Range (min … max):     2.7 ms …  15.4 ms    830 runs

Benchmark 2: lazygit --version
  Time (mean ± σ):      13.5 ms ±   2.5 ms    [User: 6.4 ms, System: 5.2 ms]
  Range (min … max):    10.2 ms …  21.2 ms    224 runs

Summary
  lazygitrs --version ran
    3.24 ± 1.16 times faster than lazygit --version

MIT

Feel free to fork and give it your own spin.