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

mycastle

v0.1.2

Published

Personal workspace toolkit: scaffold a work hub and run cross-platform read-only CLIs (Kibana / XXL-Job / Archery / MySQL / repo-changes). Skills are managed by the `skills` CLI.

Readme

mycastle

Personal workspace toolkit — scaffold a work hub and run cross-platform read-only CLIs. Skill management is delegated to the skills CLI.

Install

npm install -g mycastle

Quick start

mycastle init my-workspace     # scaffold a new workspace
cd my-workspace
mycastle env                   # print your shell/OS/toolchain

init creates docs/ + .myws/ and writes template files (README/AGENTS/CLAUDE/.gitignore). Skills install is optional — add --skills to install into .agents/skills/ + .claude/skills/ via the skills CLI (npx skills add ccor/mycastle --all; best-effort — failure only warns), or run that command later.

Commands

Workspace management:
  init [dir]            scaffold a new workspace
  self-update           update the mycastle package (npm)

Tools (run "mycastle <tool> --help" for details):
  hello                 smoke test
  env                   OS/shell/toolchain + shell quoting cheat-sheet
  changes               collect repo changes → JSON
  kibana <cmd>          read-only Kibana CLI
  xxljob <cmd>          read-only XXL-Job admin CLI
  xxljob-scan           offline-scan Java source for xxl-job handlers → JSON
  archery <cmd>         read-only Archery DB portal CLI
  mysql <cmd>           MySQL inspection + DDL execution CLI

Update

mycastle self-update      # npm update -g mycastle (updates the package only)
skills update             # refresh skills installed in this workspace

Skills are pulled from this repo's skills/ dir on GitHub by the skills CLI and tracked in .skill-lock.json — updating them does not require an npm release.

Credentials

Tools read secrets only from gitignored files under .myws/ (or env vars), never from flags. See each tool's --help. The package itself contains no secrets.

Agents must never read .myws/* files or .env raw — the contents flow into their conversation context and out to model servers. Enumerate with the redacted commands instead: mycastle mysql conns (password always "***") and mycastle archery|xxljob|kibana envs (name + url + username; never passwords).

Development

git clone <mycastle-repo>
cd mycastle
npm install
npm run build            # tsc → dist/
node dist/cli.js hello   # smoke test
npm run typecheck        # tsc --noEmit

Source layout: src/*.ts = CLI tools (each exports run(argv)); src/lib/*.ts = shared helpers; src/cli.ts = command router; src/commands/*.ts = init/self-update; skills/ = GitHub source the skills CLI pulls from (not in the npm tarball); templates/ = workspace scaffolds.