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

llm-configsync

v0.2.1

Published

Sync LLM CLI settings across machines. One command save, one command load.

Readme


New machine. Claude Code, Gemini CLI, Codex all installed — but none of your settings, MCP servers, hooks, or slash commands carried over. You're setting everything up from scratch. Again.

llm-configsync backs up all your LLM CLI configs to a private GitHub Gist and restores them anywhere in one command.

Machine A                     GitHub Gist              Machine B
                               (private)
~/.claude/*  ─┐                                   ┌─> ~/.claude/*
~/.gemini/*  ─┼── lcs save ──>  JSON bundle ──> lcs load ──┼─> ~/.gemini/*
~/.codex/*   ─┘                                   └─> ~/.codex/*

Install

npm install -g llm-configsync

Quick Start

# Machine A — save your settings
lcs init     # paste GitHub token (gist scope only)
lcs save     # done

# Machine B — restore everything
lcs init     # same token
lcs load     # done — all configs restored
lcs save

  ✓ Claude Code — 5 files, 8.2KB
    .claude/settings.json (1.5KB)
    .claude/CLAUDE.md (3.1KB)
    .claude/hooks/contextzip-rewrite.sh (1.5KB)
    .claude/skills/github-readme/SKILL.md (1.8KB)
    .claude/plugins/installed_plugins.json (348B)
  ✓ Gemini CLI — 2 files, 348B
    .gemini/settings.json (82B)
    .gemini/projects.json (266B)
  ✓ OpenAI Codex — 2 files, 1.8KB
    .codex/config.toml (612B)
    .codex/rules/default.rules (1.2KB)

  Total: 9 files, 10.4KB
  Settings 4 | MCP 0 | Hooks 1 | Skills 1 | Instructions 3

What Gets Synced

| Tool | Files synced | |:---|:---| | Claude Code | settings.json, keybindings.json, CLAUDE.md, hooks/, skills/, plugins/installed_plugins.json, plugins/known_marketplaces.json, plugins/blocklist.json, teams/ | | Gemini CLI | settings.json, projects.json, antigravity/mcp_config.json | | OpenAI Codex | config.toml, instructions.md, rules/ | | Aider | .aider.conf.yml, .aider.model.settings.yml, .aider.models.json | | Continue | .continue/.continuerc.json, .continue/config.yaml, .continue/config.ts, .continue/.continueignore | | Copilot CLI | .config/github-copilot/settings.json |

Commands

| Command | What it does | |:---|:---| | lcs init | Set up GitHub token (once per machine) | | lcs save | Upload configs to private Gist | | lcs load | Download and restore configs | | lcs list | Show detected local configs | | lcs status | Show sync status | | lcs link <gist-id> | Link to existing Gist | | lcs save --no-redact | Upload without redacting API keys | | lcs load --force | Overwrite without backups | | lcs --version | Show version | | --lang=en / --ko | Change language (auto-detected) |

Safety

  • 17 API key patterns auto-redacted — OpenAI, Anthropic, Google, AWS, GitHub, GitLab, HuggingFace, Slack, Replicate, Vercel, Supabase, and generic key-value patterns
  • Sensitive files auto-skippedauth.json, credentials.json, .env, .pem, .key files are never uploaded
  • Private Gist — only you can see it
  • Backups — existing files saved as .bak before overwriting
  • File size limit — files over 1MB are skipped; binary files auto-detected and excluded
  • Path traversal protection — validates all paths on restore
  • Token security — hidden input on entry, file permissions set to owner-only (0600)
  • Cross-platform — works on macOS, Linux, and Windows with consistent path handling
  • Zero dependencies — Node.js 18+ built-in modules only

Language

Auto-detects system locale (English/Korean). Override with --lang=en or --ko.

How It Works

lcs save:
  ~/.claude/* ──> scan ──> skip sensitive ──> redact secrets ──> JSON bundle ──> Gist API
                                                                                     |
lcs load:                                                                            |
  Gist API ──> download ──> validate paths ──> backup existing ──> write files ──────┘

No server, no database, no account to create. Just your GitHub token and a private Gist.

Adding a New Tool

Edit src/profiles.js:

{
  name: "My Tool",
  id: "my-tool",
  paths: [
    { rel: ".my-tool/config.json", desc: "Config", cat: "settings" },
    { rel: ".my-tool/plugins/", desc: "Plugins", dir: true, cat: "skills" },
  ],
}

[!TIP] PRs welcome for new LLM CLI tools. Just add the config paths.

License

MIT