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

@neatlogs/wizard

v0.0.8

Published

AI-powered CLI that instruments Neatlogs observability in your project

Readme

@neatlogs/wizard

AI-powered CLI that instruments Neatlogs observability in your project in minutes.

The wizard detects your stack (language, agent framework, LLM providers), then uses an AI agent to add Neatlogs tracing the right way for your setup — installing the SDK, wiring init(), and applying the correct instrumentation (auto-instrumentors, wrapMastra, wrapAISDK, @span/trace, etc.). It leaves behind a project-specific skill so your coding agent can keep instrumenting new code.

Usage

npx @neatlogs/wizard

Run it from your project root. All you need is your Neatlogs API key — the wizard prompts for it. Everything else is automatic. The wizard will:

  1. Detect your stack (Python/TypeScript, framework, providers).
  2. Authenticate with your Neatlogs API key (the only thing it asks for).
  3. Install the latest Neatlogs SDK and instrument your code via an AI agent following a framework-specific skill.
  4. Verify the first trace reaches your Neatlogs dashboard.
  5. Connect the Neatlogs MCP server to your coding agent (Claude Code / Cursor), so it can query your traces and detections — offered at the end; skip anytime.

You don't pick an SDK version, an endpoint, or which files to touch — the wizard always installs the latest Neatlogs SDK and figures out the rest from your codebase.

CI / advanced flags

For non-interactive runs (CI) you can pass the API key instead of being prompted:

npx @neatlogs/wizard --ci --api-key <key>

| Flag | Description | |------|-------------| | --api-key <key> | Neatlogs API key (skips the interactive prompt; required with --ci) | | --ci | Non-interactive mode | | --install-dir <path> | Project directory to instrument (default: current directory) | | --debug | Verbose output |

Commands

| Command | Description | |---------|-------------| | (default) | Full first-time setup | | scan | Re-scan for new uninstrumented code and propose instrumentation | | mcp | Install the Neatlogs MCP server only |

Supported stacks

  • Python: OpenAI / Anthropic / Google / Bedrock SDKs, LangChain / LangGraph, CrewAI, OpenAI Agents
  • TypeScript: OpenAI / Anthropic SDKs, Vercel AI SDK (wrapAISDK), Mastra (wrapMastra), LangChain

Requirements

License

MIT