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

@adikuma/evolve

v0.1.2

Published

self-improving developer toolkit for claude code

Readme

Evolve

I kept repeating myself to Claude. Every session, same corrections. "Use pnpm not npm." and "Conventional commits please." Over and over.

Then I started binding skills and slash commands manually to fix it. That worked, but it was sooo boring. I had to notice the pattern myself, write the fix myself, deploy it myself.

So I was like, maybe Claude can watch itself and write this stuff.

Install

npm install -g @adikuma/evolve
evolve setup

Then run evolve from any project directory.

Commands

| Command | What It Does | |---------|-------------| | evolve setup | First-time setup. Pick your model, time range, and how you want Evolve to run. | | evolve | The main command. Shows detected patterns, lets you pick which to deploy. | | evolve --fresh | Force a fresh analysis instead of using cached patterns. | | evolve --dry-run | See what Evolve would find without deploying anything. | | evolve --session <id> | Analyze just one specific session. | | evolve status | See what's deployed and rollback if needed. | | evolve memory | See everything Evolve has learned. Forget patterns you don't want. | | evolve insights | Analytics dashboard. Runs, patterns, deployments over time. | | evolve discover | Search the community for skills that match your patterns. |

What Evolve Can Build

| Artifact | Where It Goes | What It Does | |----------|--------------|--------------| | Skill | .claude/skills/{name}/SKILL.md | Reusable workflow you invoke with /skill-name | | Rule | CLAUDE.md | Persistent instruction Claude follows every session | | Conditional Rule | .claude/rules/{name}.md | Rule that only applies to specific file types | | Slash Command | .claude/commands/{name}.md | Lightweight prompt template | | Subagent | .claude/agents/{name}.md | Specialized agent with its own personality |

For full details on how everything works, see DOCUMENTATION.md. For diagrams and module structure, see ARCHITECTURE.md.

Planned

  • Claude Code Hooks - Evolve runs automatically when you start and stop Claude sessions.