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

@mnemonik/scanner

v5.6.2

Published

Automatic codebase indexing daemon for Mnemonik

Readme

@mnemonik/scanner

Automatic codebase indexing daemon for Mnemonik — persistent memory for AI coding assistants.

The scanner watches your project directories for code changes and indexes them so your AI assistant can find relevant files, functions, and patterns when you need them.

Installation

npm install -g @mnemonik/scanner

Quick Start

mnemonik-scanner start --key <your-api-key> --roots ~/Projects

Your API key is available on the Mnemonik dashboard. The --roots flag specifies which directories to scan for projects (comma-separated).

Configuration is saved to ~/.mnemonik/scanner.json after first run. Subsequent starts need no arguments:

mnemonik-scanner start

How It Works

  1. The daemon walks your --roots directories looking for .mnemonik.json files (created automatically by your IDE's Mnemonik integration)
  2. For each discovered project, it scans source files and pushes code chunks to the Mnemonik API
  3. It watches for file changes and incrementally updates the index
  4. Every 5 minutes, it re-scans roots to discover new projects, handle folder renames, and drop deleted projects

Commands

| Command | Description | |---------|-------------| | mnemonik-scanner start [options] | Start the daemon | | mnemonik-scanner stop | Stop the running daemon | | mnemonik-scanner status | Show daemon status and watched projects | | mnemonik-scanner log | Show recent log output | | mnemonik-scanner help | Show usage information |

Start Options

| Option | Description | |--------|-------------| | --key <api-key> | Mnemonik API key (or set MNEMONIK_API_KEY env var) | | --server <url> | Server URL (default: https://api.mnemonik.dev) | | --roots <dirs> | Comma-separated directories to scan for projects |

Configuration

The daemon saves its configuration to ~/.mnemonik/scanner.json with 0600 permissions (owner read/write only).

You can also set the API key via the MNEMONIK_API_KEY environment variable, which takes precedence over the config file and is never written to disk.

Files

| Path | Purpose | |------|---------| | ~/.mnemonik/scanner.json | Persistent configuration | | ~/.mnemonik/daemon.pid | PID file for the running daemon | | ~/.mnemonik/scanner.log | Log file (rotated at 5MB) |

What Gets Indexed

The scanner indexes code chunks (functions, classes, modules) from these file types:

.ts .tsx .js .jsx .py .rs .go .java .c .cpp .h .cs .rb .php .swift .kt .md

It respects .gitignore and skips common directories (node_modules, .git, dist, build, etc.). Only code structure is indexed — binary files and non-code assets are ignored.

Resource Usage

The daemon is designed to run continuously with minimal impact:

  • Memory: Capped at 256MB
  • CPU: Event-driven (idle when no files change)
  • Disk: Log rotation at 5MB
  • Network: Only changed files are pushed (hash-based diffing)

Requirements

  • Node.js 20 or later
  • A Mnemonik account and API key (sign up)

License

Proprietary. See mnemonik.ai/terms for details.