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

claude-code-theme-patcher

v0.2.2

Published

Patch official Claude Code installs to inject bundled and custom Hippocode themes.

Readme

Claude-themes-SpongeBob

Standalone theme package for patching official Claude Code with Hippocode Pixel themes.

The npm package published from this repository is still named claude-code-theme-patcher.

This package is the second-stage installer:

  1. it finds the official Claude Code install
  2. it chooses the right patch strategy for that install shape
  3. it backs up the original entrypoint to ~/.claude/backups/
  4. it injects bundled plus imported custom themes into a validated Claude Code runtime
  5. it can restore the original install later

Quick Start

Open-box path for bundled themes:

npx claude-code-theme-patcher init

Open-box path for your own theme pack:

npx claude-code-theme-patcher init --theme-pack ./my-themes.json

Reusable local command:

npm install -g claude-code-theme-patcher

Usage

claude-theme-patch init [theme]
claude-theme-patch list
claude-theme-patch status
claude-theme-patch install spongebob
claude-theme-patch import-theme ./my-themes.json
claude-theme-patch sync
claude-theme-patch set light-patrick
claude-theme-patch remove

Patch an unvalidated Claude Code build anyway:

claude-theme-patch --force install spongebob

Recommended user flow

Patch official Claude Code and set a usable bundled theme in one command:

npx claude-code-theme-patcher init

Patch official Claude Code and immediately use the first theme from your custom pack:

npx claude-code-theme-patcher init --theme-pack ./my-themes.json

Pick a specific theme during init:

npx claude-code-theme-patcher init jellyfish-fields --theme-pack ./my-themes.json

Switch later without reinstalling or re-importing:

npx claude-code-theme-patcher set bubble-bass

If you already initialized once, import an updated custom pack and refresh the patch:

npx claude-code-theme-patcher import-theme ./my-themes.json
npx claude-code-theme-patcher set jellyfish-fields

Or install once globally, then reuse the local command:

npm install -g claude-code-theme-patcher
claude-theme-patch init
claude-theme-patch set bubble-bass

Files

  • Claude Code config: ~/.claude.json
  • Patch metadata: ~/.claude/hippocode-theme-patch.json
  • Imported custom theme pack: ~/.claude/hippocode-custom-themes.json
  • Managed Claude runtime cache: ~/.claude/hippocode-managed-runtime/
  • Backups: ~/.claude/backups/

Custom Theme Pack Format

Custom themes are imported from JSON and expanded into a dark + light pair automatically.

{
  "themes": [
    {
      "name": "jellyfish-fields",
      "displayName": "Jellyfish Fields",
      "accent": "#b982ff",
      "shimmer": "#e9d5ff",
      "promptBorder": "#7d5fa8"
    }
  ]
}

Notes:

  • name becomes name and light-name
  • colors accept #rrggbb, #rgb, or rgb(r,g,b)
  • displayName, shimmer, and promptBorder are optional
  • importing a theme with the same name updates the saved definition

Notes

  • On classic JS-based Claude Code installs, this tool patches the official cli.js in place.
  • On newer npm-wrapper installs that ship a native bin/claude.exe, init installs a managed validated Claude Code runtime under ~/.claude/hippocode-managed-runtime/ and swaps the wrapper entrypoint to launch that patched runtime.
  • remove restores the original official launcher and deletes the managed runtime cache for that install.
  • Version-specific patch matchers live under src/adapters/; add a new adapter instead of growing src/cli.ts.
  • This release is validated against Claude Code 2.1.112.
  • When Claude Code updates, you may need to rerun the patcher or publish a new patcher build.
  • Use --target <path> to patch a copied cli.js or a copied official wrapper during testing instead of touching the real install.
  • init is the shortest supported user path; it patches Claude Code and sets a theme in one command.
  • status reports whether the detected Claude Code version is inside the validated set.
  • install blocks unvalidated Claude Code versions unless you pass --force.
  • import-theme persists custom theme seeds and refreshes the current patch automatically when metadata is available.
  • sync rebuilds the installed patch using the current saved custom theme pack.
  • After patching, users can switch official, bundled, and imported custom themes from Claude Code /theme or via claude-theme-patch set <theme>.

Release Check

npm run verify:release

Publishing

This repository now includes a GitHub Actions publish workflow at .github/workflows/publish.yml.

Release docs:

  • Current release body: docs/releases/v0.2.1.md
  • Native-wrapper release body: docs/releases/v0.2.2.md
  • Next automated release checklist: docs/releases/0.2.2-checklist.md
  • Project changelog: CHANGELOG.md

One-time npm setup:

  1. Create or claim the claude-code-theme-patcher package on npm.
  2. In npm package settings, add a trusted publisher for:
    • GitHub user or org: sqoder
    • Repository: Claude-themes-SpongeBob
    • Workflow filename: publish.yml
  3. After the first successful publish, restrict package publishing to trusted publishing on npm.

Release flow:

  1. Bump package.json to the version you want to ship.
  2. Push that commit to main.
  3. Create a GitHub Release with tag v<package.json version>.
  4. The publish workflow will run npm run verify:release and then npm publish.

Notes:

  • The workflow uses npm trusted publishing through GitHub Actions OIDC.
  • package.json already points repository.url at https://github.com/sqoder/Claude-themes-SpongeBob.git, which npm requires to match the publishing repository for trusted publishing.
  • npm package claude-code-theme-patcher is published publicly on npm.

Development

npm install
npm run build
npm run smoke