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

bigstarter

v0.1.1

Published

The Kickstarter for vibe coding — MCP plugin for building in public with AI agents

Downloads

349

Readme

bigstarter

The Kickstarter for Vibe Coding — a local MCP plugin that lets AI-assisted projects build in public.

What it does

  • Records every architectural decision to .kap/decisions/ in your GitHub repo
  • Generates public updates automatically after commits/milestones via LLM sampling
  • Reads community signals from GitHub Issues
  • Hooks framework for audit, circuit-breaking, and conventional commits

Install

npx bigstarter init

This creates:

  • .kap/kap.json — your project metadata
  • .mcp.json — MCP server config (gitignored, has your GitHub token)
  • .github/workflows/bigstarter-reporter.yml — auto-updates on push/PR/release

And opens a PR on the BigStarter registry to list your project on the platform.

Configure in Claude Code

Global config — configure once, works in every project:

Add to ~/.claude/settings.json:

{
  "env": {
    "GITHUB_TOKEN": "ghp_xxx"
  },
  "mcpServers": {
    "bigstarter": {
      "command": "npx",
      "args": ["bigstarter"]
    }
  }
}

That's it. BigStarter auto-detects GITHUB_OWNER, GITHUB_REPO, and KAP_PROJECT_ID from:

  1. .kap/kap.json in the current project directory (authoritative)
  2. git remote get-url origin (fallback)
  3. The directory name (last resort)

Per-project override (optional) — only if you need non-standard values:

{
  "env": {
    "GITHUB_OWNER": "your-username",
    "GITHUB_REPO": "your-repo",
    "KAP_PROJECT_ID": "custom-id"
  }
}

Available tools

| Tool | When to use | |------|-------------| | kap_report_event | After commits, milestones, deploys | | kap_pkg_write | After architectural decisions | | kap_pkg_build_context | At session start | | kap_fetch_feedback | Before sprint planning | | kap_pkg_query | Before implementing a known pattern | | kap_escalate_to_admin | When a decision exceeds your autonomy |

Resources (via @mention)

  • @kap://decisions — recent architectural decisions
  • @kap://vision — project vision
  • @kap://signals — community signals

Platform

All projects with .kap/kap.json appear on bigfatdot.github.io/BigStarter.

License

MIT