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

@inkvi/jean-claude

v1.4.0

Published

Sync Claude Code configuration across machines using Git

Readme

JEAN-CLAUDE

A companion for syncing Claude Code configuration across machines

Why?

You've spent hours crafting the perfect CLAUDE.md. Your hooks are chef's kiss. Your settings are dialed in just right.

Then you sit down at another machine and... nothing. Back to square one.

Jean-Claude fixes that. It syncs your Claude Code configuration across all your machines using Git.

What gets synced?

  • CLAUDE.md - Your custom instructions
  • settings.json - Your preferences
  • hooks/ - Your automation scripts
  • skills/ - Your custom skills

Quick Start

# Install globally
npm install -g jean-claude

# Verify install
jean-claude --help

# Initialize Jean-Claude and link to your config repo
jean-claude init [email protected]:YOURUSER/jean-claude-config.git

# Make edits in ~/.claude, then push them
jean-claude push

# Pull the canonical config and apply it locally
jean-claude pull

# Check whether this machine is in sync
jean-claude status

That's it!

Four commands. No options. No complexity. Just sync.

Development

Running Tests

Jean-claude has both unit tests and integration tests:

# Run all tests (unit + integration)
npm test

# Run only unit tests (fast)
npm run test:unit

# Run unit tests in watch mode
npm run test:unit:watch

# Run with coverage report
npm run test:coverage

# Run only integration tests
npm run test:integration

Unit Tests

Fast, isolated tests for core logic:

  • File sync and metadata operations
  • Error handling and types
  • Utility functions

Integration Tests

End-to-end tests that simulate real usage with a local git repository and multiple machines:

  • init command: New repos, existing repos, already initialized, invalid remotes
  • push command: Initial files, no changes, modifications, new hooks
  • pull command: Basic sync, overwriting local changes, not initialized
  • status command: Clean state, uncommitted changes, not initialized
  • Sync scenarios: Bidirectional sync between machines
  • Edge cases: Empty directories, special characters, large files, multiple hooks, concurrent modifications, nested directories
  • Metadata: Persistence, timestamp updates

See tests/README.md for more details.


Named after the famous Belgian martial artist and philosopher, because your config deserves to do the splits across multiple machines.