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

@nfinitmonkeys/clan

v0.26.0

Published

Universal clan runtime for the Jungle — set up an AI agent for any project, anywhere. Persistent brain by default + one-shot `wild` install for standalone Claude Code integration.

Readme

@nfinitmonkeys/clan

Universal clan runtime for the Jungle — set up an AI agent (an Alpha) for any project, on any machine, with a persistent brain by default.

⚠️ Always use the scoped name @nfinitmonkeys/clan. The bare jungle-clan is unpublished on npm and squattable. And never npm install -g — a stale global silently shadows npx.

Quick Start — up is the door

npx -y @nfinitmonkeys/clan up

One command, one flow: a short interview (what is this clan for? what should the Alpha be called?) → the engine plans exactly what it will write → you approve → it applies (backed up, journaled, undoable) → doctor verifies.

Inside Claude Code the same door is conversational: type /clan:up.

Re-running up on an existing clan is a repair, not an error — it brings an old clan to the current standard and writes nothing if you're already there.

Scripted / automation paths

# Non-interactive standalone (no prompts):
npx -y @nfinitmonkeys/clan up --yes --alpha Relay --name my-project

# Attach to a pre-provisioned clan (credentials via env, never argv):
ALPHA_ID=<uuid> JUNGLE_API_KEY=<key> npx -y @nfinitmonkeys/clan up --yes --attach

# The classic one-shot doors still work and run the same engine:
npx -y @nfinitmonkeys/clan attach --alpha-id <uuid> --api-key <key>   # join a Jungle
npx -y @nfinitmonkeys/clan wild --yes --alpha Relay                   # standalone, no Jungle

What setup writes

All setup paths drive @nfinitmonkeys/clan-engine — a single deterministic, non-destructive authority (dry-run plans, uniform backups, journaled undo):

  • .jungle/config.yaml — identity + credentials (gitignored)
  • CLAUDE.md — geo-tier declaration (your existing prose is untouched)
  • .claude/skills/clan-awareness/SKILL.md — the awareness skill
  • .claude/commands/clan/*.md — the /clan:* slash commands (incl. /clan:up)
  • .mcp.json — a jungle-local MCP server merged alongside any servers you already have (connected mode; gitignored — it holds a live key)
  • .claude/settings.json — a SessionStart hook that hydrates the brain
  • .brain/ — the versioned memory vault
  • .clan/inventory.json — your existing agents/skills/commands, so the Alpha works with them instead of duplicating

The brain

# Seed the brain from what the project already knows (dry-run by default):
npx -y @nfinitmonkeys/clan brain build --write

# Add Claude Code session memory as a source:
npx -y @nfinitmonkeys/clan brain build --write --memory

# Have this clan's configured LLM rewrite the mined pages into real
# identity/hot/index/concept prose (grounded, re-scanned, graceful fallback
# to mechanical pages if the LLM is unavailable or misbehaves):
npx -y @nfinitmonkeys/clan brain build --write --curate

# Ask the brain a question — works on ANY configured provider:
npx -y @nfinitmonkeys/clan brain query "what is this project's deploy story?"

brain build mines README, docs/, CLAUDE.md, manifests, and code. Every source — and every curated page — is scanned for secrets/infra-ids/PHI first; anything sensitive is held back and reported, never written. Create-only: your accumulated pages are never touched.

brain query runs on cortex, openai, anthropic, or ollama — whatever set-llm configured. No vendor wall.

LLM configuration

npx -y @nfinitmonkeys/clan set-llm --provider cortex --key sk-cortex-...
# or: --provider ollama | openai | anthropic  (plus --base-url / --model)

Config lives in .jungle/config.yaml (gitignored) with an llm: block:

llm:
  provider: cortex        # ollama / openai / anthropic / cortex
  baseUrl: https://...
  apiKey: sk-...
  model: ...

Day-to-day commands

| Command | Description | |---------|-------------| | up [flags] | The ONE door — interview → plan → approval → apply → doctor | | attach / wild | Scripted setup paths (join a Jungle / standalone) | | set-llm | Configure the LLM (provider / key / base-url / model) | | brain build [--curate] | Seed the brain from existing files | | brain query "<q>" | Ask the brain (any configured provider) | | brain init / brain lint | Scaffold / health-check the vault | | start / stop | Run the Alpha (polling loop) | | serve | Local browser UI — chat with your clan in a tab | | status [--json] | Clan status (live from the Jungle when connected) | | talk "msg" | Talk to your Alpha | | inbox / thread <id> | Read messages | | policies | View governance policies | | health | Probe + report health to the Jungle (connected mode) |

Verify / repair / undo

npx -y @nfinitmonkeys/clan-engine doctor   # validate config, mcp name, brain, hook, creds
npx -y @nfinitmonkeys/clan-engine plan     # see exactly what a re-run would change
npx -y @nfinitmonkeys/clan-engine undo     # reverse the last apply

License

MIT