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

@nodehunter/core

v0.0.1

Published

Pure domain engine for nodehunter — scan, size, workspace analysis, and delete.

Downloads

39

Readme

@nodehunter/core

Pure TypeScript engine for nodehunter — the same scan, size, workspace, and delete logic as the CLI, without shelling out.

No console.* and no process.* in core — your host passes HostOperationContext (platform, scan path, flags) so the same code runs in Node scripts, CI, and custom tools.

Install

Requires Node.js >= 18.

npm install @nodehunter/core
# or: pnpm add @nodehunter/core

CLI package vs SDK package

| Install | Best for | |---------|----------| | npm install nodehunter | Terminal CLI — self-contained binary plus optional nodehunter/core import from the same tarball (not a runtime dep on @nodehunter/core) | | npm install @nodehunter/core | Apps, CI jobs, and libraries that embed scan/size/delete without the CLI binary (recommended for imports) |

You do not need both for most projects. Pick the CLI for command-line use, or @nodehunter/core when you import APIs directly.

Quick start

import {
  createHostRunSession,
  createSuggestionHostContext,
  resolveHostPlatform,
  runScan,
} from '@nodehunter/core';

const ctx = {
  runtime: {
    cwd: process.cwd(),
    platform: resolveHostPlatform(process.platform),
  },
  scan: { path: process.cwd() },
  suggestions: createSuggestionHostContext(process.platform),
  session: createHostRunSession(),
};

const { analysis, output } = await runScan(ctx);

Runnable examples: examples/sdk/ in the nodehunter repository.

Subpath exports

| Subpath | Stability | Purpose | |---------|-----------|---------| | @nodehunter/core | stable | Public SDK surface (runScan, runSize, envelopes, …) | | @nodehunter/core/shared | stable | Shared scanner helpers and constants | | @nodehunter/core/advanced | advanced | Low-level run emitters | | @nodehunter/core/internal | internal | CLI host globals — not for external apps |

Run pnpm exports:validate in the monorepo before releases.

Documentation

License

MIT