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

@vd7/gitty

v0.6.14

Published

snapshot checkpoint CLI: gitty + gittysnap + gittyunion (content first)

Readme

GitHub npm


flowchart LR
  T[tree] --> Q{can this path land?}
  Q -->|yes| P[commit + push]
  Q -->|conflict / too big / submodule| H[hold back]
  P --> R[keep going]
  H --> R
  R --> F{anything still blocked?}
  F -->|held some| D[remote has the rest]
  F -->|nothing landed| K[park bak/pending-merge]

Issue

❌ All-or-nothing stall

  • one conflicted, oversized, or submodule path parks the whole checkpoint

  • the rest of the tree sits unbacked on that machine

  • drip: push the clean subset; hold the rest; never stall the backup

❌ Dual-machine strand

  • laptop + desktop both edit

  • N local commits replay against remote -> same conflict N times

  • other machine's work never left that machine

❌ Checkpoint friction

  • agents touch many repos per session

  • add + commit + push per repo burns time

  • one blocker used to abort the whole run

❌ Append ledger false conflicts

  • two hosts append different .ndjson / .jsonl lines

  • git sees one slot, two lines -> conflict

  • nothing was edited; both lines should keep

Options

| | Bin | Job | When | |---|---|---|---| | | gitty | drip + holdback -> commit -> push | default backup | | | gittylfs | same + LFS track | big binaries | | | gittyembedded | submodules then parent | dirty nested repos | | | gittyhealth | report only | inspect / mid-op | | | gittysnap | snap -> merge -> abort clean | solo multi-machine | | | gittyunion | NDJSON union driver | append ledgers |

Separate bins. Same package. Plain gitty != gittysnap.

Setup

# scoped package; same bin names
npm i -g @vd7/gitty

Optional resolvers (missing file -> empty allowlist -> drip/park, no auto-resolve):

per_host:
  paths:
    - registry/system-resource/manifest.json
  globs:
    - snapshots/$(hostname)/**
semantic_union:
  globs:
    - "**/*.ndjson"
    - "**/*.jsonl"
  key_field: ts

Usage

| path | do this | get this | |---|---|---| | A | gitty | drip + holdback checkpoint on remote | | B | gittysnap | snapshot-first solo sync | | C | gittyunion install | NDJSON union merge driver |

Path A · gitty

# land whatever can land; hold blockers; park only if nothing can
gitty "checkpoint" "$HOME/Documents/a/gitty"

GITTY_PARTIAL=1 default. Park-only: GITTY_PARTIAL=0. Bulldoze: GITTY_FORCE=1.

Path B · gittysnap

# both hosts on remote first; rc=2 on conflict; worktree clean
gittysnap

Path C · gittyunion

# union + dedupe + stable-sort for .ndjson / .jsonl
gittyunion install

Output

| signal | meaning | |---|---| | partial integrate | resolved subset committed; held paths stay local | | holdback | oversized / submodule / push-reject left unstaged | | park | nothing could land; bak/pending-merge-* + remote-snapshot-* |

Local branch stays put on park. Nothing lost.

Gotchas

| problem | fix | stability | why | |---|---|---|---| | one unresolvable file parks whole merge | drip (GITTY_PARTIAL=1): commit resolved subset | stable | backup as much as possible | | oversized path blocks push | leave GITTY_PARTIAL=1 | stable | hold back; push the rest | | N-commit rebase replays same conflict N times | merge --ff-only then --no-ff once | stable | one merge, one conflict set | | per-host artifact conflicts every sync | .gitty/additive-resolvers.yaml per_host | stable | ours on that host; --no-ff keeps both parents | | .ndjson append conflict | semantic_union or gittyunion install | stable | union + dedupe + stable-sort | | fresh clone drops union driver | re-run gittyunion install | stable | attrs alone insufficient | | nothing can land | park bak/pending-merge-* | stable | first-class ref; nothing lost; non-fatal | | foreign-owned .git (old sudo git) | sudo chown -R "$(whoami)" .git | stable | fail-fast; GITTY_SKIP_PERM_CHECK=1 opt out |

Docs

| Doc | Topic | |---|---| | docs/README | index | | docs/commands | all bins | | docs/gittysnap | snapshot-first sync | | docs/gittyunion | NDJSON union driver | | docs/partial-commit | holdback + drip | | docs/environment | env | | docs/hooks | repo hooks |

npm tarball = bin/ + README only. docs/ is GitHub.

Contact