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

devmind-monitor

v0.1.0

Published

Production monitoring SDK for DevMind — captures errors, sends them to DevMind agents for autonomous triage + memory-based incident response.

Downloads

153

Readme

devmind-monitor

Lightweight production monitoring SDK for DevMind. Captures errors and forwards them to DevMind agents, which then triage the incident, search your team's memory for prior similar incidents, and propose a fix — autonomously.

Think of it as Sentry + an autonomous incident-response engineer that remembers everything your team ever learned.

Install

npm install devmind-monitor

Quick start

import { DevMindMonitor } from 'devmind-monitor';

const monitor = new DevMindMonitor({
  apiUrl: 'https://api.devmind.app',
  apiToken: process.env.DEVMIND_TOKEN!,
  workspaceId: process.env.DEVMIND_WORKSPACE!,
  service: 'checkout-api',
});

monitor.attachToProcess();

That's it. Any uncaught error or unhandled rejection on this process will:

  1. Be captured locally (zero overhead — it's just a process.on hook)
  2. Be forwarded to your DevMind backend
  3. Trigger a 3-agent pipeline (Triage → Researcher → Responder)
  4. Show up in your DevMind dashboard at /incidents with a suggested fix within ~30 seconds

Manual reporting

For app-level events (caught errors, business-logic alerts, etc):

await monitor.reportIncident({
  type: 'error',
  severity: 'critical',
  message: 'Payment service unreachable',
  metadata: { customerId: '...', orderId: '...' },
});

Config

| Option | Required | Default | Description | |---|---|---|---| | apiUrl | yes | — | DevMind backend URL | | apiToken | yes | — | dm_sk_* token (generate at /connect) | | workspaceId | yes | — | Target workspace | | service | no | — | Logical service name (e.g. "checkout-api") | | hostname | no | os.hostname() | Instance identifier | | verbose | no | true | Console.error on transport failures | | redactPatterns | no | DM tokens, Stripe, JWT, AWS, password=, bearer ... | Regex patterns redacted before send | | defaultSeverity | no | critical | Severity for auto-captured exceptions |

What gets sent

POST {apiUrl}/incidents
{
  workspaceId,
  type: 'error' | 'attack' | 'performance' | 'custom',
  severity: 'low' | 'medium' | 'high' | 'critical',
  service: string,
  hostname: string,
  message: string,    // redacted
  stack: string,      // redacted
  metadata: object,
}

Privacy

The SDK redacts common secrets before sending (DevMind tokens, Stripe keys, JWTs, AWS keys, password= query params, bearer headers). You can pass your own redactPatterns for custom rules.

For full data sovereignty, self-host DevMind backend (docker compose up from the monorepo) and point apiUrl to your own instance — DevMind team will never see your data.

License

MIT