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

githops

v0.6.1

Published

Git hooks manager with YAML configuration

Readme

githops

Git hooks manager with YAML configuration. Declare your hooks once, commit the file, sync once — everyone on the team gets the same hooks automatically.

License: MIT Crates.io


Why

Git hooks live in .git/hooks/, which is not committed to the repository. New team members miss them. The same linting command gets copy-pasted into three different hooks. There is no single place to see what runs and why.

githops solves this with a single githops.yaml file that you commit. It supports reusable command definitions, parallel execution, dependency ordering, content-based caching, and a browser-based visual graph of your entire hook configuration.

Installation

macOS

# Apple Silicon
curl -fsSL https://github.com/vitalics/githops/releases/latest/download/githops-latest-aarch64-apple-darwin.pkg -o githops.pkg
sudo installer -pkg githops.pkg -target /

# Intel
curl -fsSL https://github.com/vitalics/githops/releases/latest/download/githops-latest-x86_64-apple-darwin.pkg -o githops.pkg
sudo installer -pkg githops.pkg -target /

Linux

curl -fsSL https://github.com/vitalics/githops/releases/latest/download/githops-latest-x86_64-unknown-linux-gnu.tar.gz | tar xz
sudo mv githops /usr/local/bin/

Windows — download and run the .msi installer from the releases page.

Cargo

cargo install githops

npm / pnpm

npm install --save-dev githops
# or
pnpm add --save-dev githops

Quick start

# 1. Initialize in any git repository
githops init

# 2. Edit githops.yaml
# 3. Install the hooks
githops sync

Example githops.yaml:

# yaml-language-server: $schema=.githops/githops.schema.json

hooks:
  pre-commit:
    enabled: true
    parallel: true
    commands:
      - name: lint
        run: npm run lint
      - name: typecheck
        run: npx tsc --noEmit
        cache:
          inputs:
            - "src/**/*.ts"
          key:
            - tsconfig.json

Features

  • Single YAML file — all hooks in one place, committed to the repository
  • Reusable definitions — extract common commands with $ref, no copy-pasting
  • YAML anchors — standard YAML &anchor / *alias for sharing config fragments
  • Parallel executionparallel: true runs commands concurrently within a hook
  • Dependency orderingdepends ensures commands run in the right sequence
  • Content-based caching — skip commands when their input files have not changed
  • Visual graph UIgithops graph --open shows and edits the full dependency graph in a browser
  • Shell completionsgithops completions init for bash and zsh
  • Self-updategithops self-update upgrades the binary in place
  • No runtime dependency — single Rust binary, works on macOS, Linux, and Windows

Commands

| Command | Description | |---|---| | githops init | Create githops.yaml and write the JSON Schema | | githops sync | Install configured hooks into .git/hooks/ | | githops sync --force | Overwrite hooks not managed by githops | | githops graph | Start the visual graph UI (add --open to open browser) | | githops check | Run all configured hooks without a git event | | githops migrate | Import configuration from Husky, lefthook, or pre-commit | | githops completions init | Install shell completions for the current shell | | githops self-update | Download and install the latest release | | githops self-update --check | Check if an update is available |

Documentation

Full documentation is available at /docs when running githops graph, or in the docs/ directory:

Russian documentation is available in docs/ru/.

Repository structure

githops/
├── src/                  # CLI binary (clap commands)
├── githops-core/         # Core library (config, sync, schema)
├── graphui/              # Visual graph UI (Axum + React/Vite)
│   └── ui/               # Frontend (TypeScript, Tailwind, React Router)
├── docs/                 # Documentation source
│   ├── en/               # English
│   └── ru/               # Russian
├── scripts/              # Release scripts
└── wix/                  # Windows installer (WiX v3)

License

MIT — see LICENSE.