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

@yogesh5770/autoheal-setup

v1.0.0

Published

AutoHeal interactive setup wizard — GitHub, Vercel & N8N in 60 seconds

Readme

@autoheal/setup

Interactive CLI wizard that connects AutoHeal to GitHub, Vercel, and N8N in under 60 seconds.

What it does

When you run this wizard it will:

  1. GitHub — Login via browser OAuth (or paste a PAT). Optionally create a new repo for your project.
  2. Vercel — Login via vercel CLI or paste an API token. Creates a project linked to your GitHub repo and generates a deploy hook.
  3. N8N — Guide you to deploy N8N on Render (free) and configure the AutoHeal Git Bridge webhook.
  4. Config — Writes .autoheal.json (non-secret) and .env.local (secrets). Updates .gitignore. Syncs settings to your AutoHeal dev server automatically.

Usage

Option A — Run once manually

npx @autoheal/setup

Option B — Auto-run on npm install

Add to your package.json:

{
  "scripts": {
    "postinstall": "autoheal-setup"
  }
}

Option C — As part of your dev setup

npm run setup

Add to your package.json:

{
  "scripts": {
    "setup": "autoheal-setup"
  }
}

Requirements

  • Node.js ≥ 18
  • Zero external dependencies (uses only built-in Node.js modules)

The Full Auto-Heal Flow After Setup

Error detected on your website
    ↓
AutoHeal AI generates a fix
    ↓
Fix written to disk locally
    ↓
gitBridge.dispatch() called automatically
    ↓
POST → N8N Webhook (your Render instance)
    ↓
N8N commits fix to GitHub
    ↓
GitHub triggers Vercel/Render rebuild
    ↓
Live website heals itself ✓

Files Created

| File | Contents | |---|---| | .autoheal.json | Non-secret config (repo name, N8N URL, Vercel project URL) | | .env.local | Secret tokens (GitHub PAT, Vercel token, deploy hook) |

⚠️ Never commit .env.local — it contains your secret tokens. The wizard adds it to .gitignore automatically.

N8N Workflow

After running this wizard, import the n8n_git_bridge_workflow.json file into your N8N instance:

  1. Open your N8N dashboard (e.g. https://my-n8n.onrender.com)
  2. Go to Workflows → Import from File
  3. Select n8n_git_bridge_workflow.json
  4. Add your GitHub credentials in the GitHub node
  5. Activate the workflow

Re-running the Wizard

You can safely re-run the wizard at any time to update credentials:

npx @autoheal/setup

Existing values are pre-filled so you only need to update what changed.