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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@roeus/gitsync

v1.0.1

Published

CLI to check git sync status of repos in current directory

Readme

gitsync

npm version license node

CLI tool that scans directories for git repos and reports their sync status.

Demo

Why gitsync?

Working across multiple git repositories? It's easy to forget uncommitted changes, unpushed commits, or branches without upstreams.

gitsync gives you a quick overview of all repos in a directory so nothing falls through the cracks.

Features

  • Detect uncommitted changes
  • Track ahead/behind status vs remote
  • Find branches without upstream tracking
  • Multiple output formats: JSON, table, minimal
  • Recursive directory scanning
  • Config file support (cosmiconfig)

Install

npm install -g @roeus/gitsync

Or build locally:

git clone https://github.com/syz51/gitsync.git
cd gitsync
pnpm install
pnpm run build
pnpm link --global

Usage

gitsync [options] [paths...]

Options

| Flag | Description | | --------------------- | -------------------------------------------------- | | -a, --all | Show all repos (not just outstanding) | | -f, --format <type> | Output: json, table, minimal (default: json) | | -q, --quiet | Suppress output | | -r, --recursive | Scan recursively | | -d, --depth <n> | Max depth (default: 1) | | --include-hidden | Include hidden directories | | --filter <types> | Filter: changes,ahead,behind,untracked | | --dir <path> | Config file search directory |

Examples

# scan current dir, show only repos with issues
gitsync

# show all repos as table
gitsync -a -f table

# recursive scan, filter to repos with uncommitted changes
gitsync -r --filter changes

# scan specific directories
gitsync ~/projects ~/work

# combine filters
gitsync --filter changes,ahead

Config File

Supports .gitsyncrc, .gitsyncrc.json, .gitsyncrc.yaml, gitsync.config.js, or package.json field.

Example .gitsyncrc.json:

{
  "format": "table",
  "recursive": true,
  "depth": 2
}

CLI args override config file values.

Output

By default shows repos with issues:

  • uncommitted changes
  • ahead/behind remote
  • no upstream
  • untracked branches

JSON (default)

[{"name": "repo", "uncommittedChanges": 3, "ahead": 1, ...}]

Table

REPO     BRANCH  CHANGES  AHEAD  BEHIND  UNTRACKED
my-repo  main    3        1      0       feature-x

Minimal

my-repo (main): 3 changes, 1 ahead, [feature-x]

Requirements

  • Node.js >= 24
  • git

Development

git clone https://github.com/syz51/gitsync.git
cd gitsync
pnpm install
pnpm run build

# test locally
pnpm link --global
gitsync

Contributing

  1. Fork the repo
  2. Create a feature branch
  3. Make changes
  4. Submit a PR

License

MIT