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

ncheta

v0.1.2

Published

Ncheta — webhook memory. SDK for Node.js.

Readme

ncheta

your webhooks just got memory.

ncheta (igbo: memory / remembrance) is a self-hostable webhook monitoring tool. it intercepts incoming webhooks, stores the raw request before your handler runs, then forwards it. if your handler crashes — the data is safe. fix the bug. replay. done.

no more "stripe sent it once and we missed it."

how it works

[Stripe] ──POST──> [ncheta :7000] ──stores──> [SQLite]
                        │
                        ├── returns 200 to Stripe immediately
                        │
                        └── forwards to your handler in background
                                │
                                ├── handler returns 200? done.
                                └── handler returns 500? retry with backoff.

two ports. one binary.

  • port 7000 — ingestion. webhook senders POST here.
  • port 7001 — control API. list events, inspect payloads, trigger replays.

quickstart

rust binary

cargo build --release
./target/release/ncheta

node sdk

npm install ncheta
const { Ncheta } = require("ncheta");

const ncheta = new Ncheta();
await ncheta.start();

// express middleware — captures everything, blocks nothing
app.post("/webhooks/stripe",
  ncheta.watch({ endpointName: "stripe", targetUrl: "http://localhost:3000/webhooks/stripe" }),
  (req, res) => {
    // your handler. if this blows up, ncheta has the raw request.
    res.json({ ok: true });
  }
);

config

all env vars. all optional. sane defaults.

| var | default | what it does | |-----|---------|-------------| | NCHETA_DB_URL | sqlite://./ncheta.db | database connection | | NCHETA_INGESTION_PORT | 7000 | where webhooks land | | NCHETA_CONTROL_PORT | 7001 | REST API + dashboard | | NCHETA_MAX_BODY_SIZE | 524288 (512KB) | max request/response body | | NCHETA_MAX_RETRIES | 5 | retries before giving up | | NCHETA_EVENT_TTL_SECONDS | 604800 (7 days) | auto-cleanup after this |

api

ingestion (port 7000)

POST /in/{endpoint_name}  →  200 { "received": true, "event_id": "..." }

control (port 7001)

GET  /health              →  200 { "status": "ok" }
GET  /endpoints           →  list all endpoints
POST /endpoints           →  register a new endpoint
GET  /events              →  list events (filters: ?status=&endpoint_id=&limit=)
GET  /events/{id}         →  full event detail with headers + body
GET  /events/{id}/attempts → delivery attempt history
POST /events/{id}/replay  →  202 re-deliver the event

replay

# event failed? fix your handler, then:
curl -X POST http://localhost:7001/events/{id}/replay

# ncheta re-sends the exact same headers + body
# adds X-Ncheta-Replay: true so you know it's a replay

retry backoff

failed deliveries retry automatically:

| attempt | delay | |---------|-------| | 1 | 30 seconds | | 2 | 5 minutes | | 3 | 30 minutes | | 4+ | 2 hours |

after max_retries failures → event goes to dead status. replay manually whenever you're ready.

architecture

  • rust binary — axum + tokio + sqlx
  • sqlite with WAL mode — fast writes, no external db needed
  • zero mutex — all mutable state lives in the db
  • single reqwest client — connection pooling, no fd exhaustion
  • store-before-ack — db write completes before 200 is returned to sender

license

MIT