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

max-processor-output-viewer

v1.0.0

Published

Visualize the JSON output of the max-processor-output service: bounding boxes (group/block/shelf/product), product dots, and the full data structure in an interactive browser viewer.

Readme

max-processor-output-viewer

Interactive visualizer for the JSON output of the max-processor-output service (omniplatform/OmniServices/max-processor-output). It draws every bounding box — group / block / shelf / product — plus product dots in the original pixel coordinate space, and lets you inspect the full data structure of any item.

Zero dependencies — just Node (>= 14). Runs via npx, opens a local page in your browser.

Usage

# from a file
npx max-processor-output-viewer output.json

# from a pipe (e.g. straight from curl / a log)
cat output.json | npx max-processor-output-viewer

# no input — paste JSON in the browser
npx max-processor-output-viewer

During local development (from this directory):

node cli.js path/to/output.json

Options

| Option | Description | | --- | --- | | -p, --port <n> | Port to listen on (default: a random free port) | | --no-open | Don't auto-open the browser | | -h, --help | Show help |

What it shows

  • Bounding boxes for groups (dashed grey), blocks (colored, labeled block N · shelves×columns), shelves (S<n>), and products (colored, labeled with SKU).
  • Product dots (productDot) placed in the inferred image space.
  • Reference product (referenceProduct) marked with a ★.
  • Empty facings (isEmpty) drawn dashed; unclassified products drawn with a dotted border.

Interaction

  • Scroll to zoom, drag to pan, Fit to reset the view.
  • Hover a product for a quick tooltip; click it for a full detail panel (all fields + raw JSON).
  • Structure tree (block → shelf → column → product) on the left; click a leaf to select and center it.
  • Color by block, group, confidence (cossum, red→green gradient), or SKU.
  • Search SKU to highlight all matching facings and dim the rest.
  • Layer toggles for groups / blocks / shelves / products / dots / labels / empty facings / reference.
  • Summary stats: block/shelf/product/unique-SKU counts, average cossum, low-confidence count, empty facings, groups.

Input format

Accepts either the full response wrapper ({ "data": { … }, "taskId": … }) or a bare data object. Multiple concatenated JSON documents (batch output) are supported — a document selector appears in the header, and stray/garbage fragments between documents are skipped.

How coordinates are interpreted

All boxes use the service's pixel coordinates (x, y, w, h) with y increasing downward, matching image space. productDot is normalized 0..1; the viewer infers the image dimensions from the products' box centers vs. their dots to place the dots and draw a dashed image frame.