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

@zaowu-labs/data

v1.2.1

Published

ZaoWu data workflows

Readme

@zaowu-labs/data

Data workflow package for ZaoWu.

This package reads CSV, TSV, JSON, and XLSX inputs for inspection, lightweight analysis, schema inference, sampling, and preview-first cleaning. XLSX support uses the official SheetJS 0.20.3 distribution because the npm registry package is no longer the current upstream release channel.

Schema inference recognizes numbers, booleans, ISO or MM/DD/YYYY calendar dates, percentages, common currency values, strings, empty columns, and mixed columns without changing the source values. JSON column names are normalized for display while values are read from their original keys, so whitespace and duplicate normalized names do not lose data. Absent fields remain empty even when their names match JavaScript prototype keys.

Safety:

  • Cleaning previews by default when an output path is supplied.
  • Confirmed writes refuse to overwrite the input file or an existing output.
  • XLSX support requires explicit sheet selection when the first sheet is not the intended input.

Real-input limits and analysis

All inputs are bounded to 20 MiB. Tables allow 250,000 data rows, 1,024 columns, and two million rectangular cells including the header. XLSX is checked against an actual 64 MiB inflated-byte budget and 2,000 archive entries before SheetJS parsing. Oversized worksheet ranges fail before sparse cells are enumerated. No data is silently truncated to fit a limit.

Numeric count, min, max, and average use finite numeric cells only; missingCount and nonNumericCount explain excluded cells. Leading-zero IDs, units such as 20kg, and numeric overflow remain non-numeric source values. A scaled compensated mean avoids overflow on finite extreme values.

Extra unnamed columns receive stable column_N headers instead of losing data. JSON accepts an object or arrays of objects, preserves nested values as JSON cell text, and rejects primitive/mixed arrays. Unclosed CSV quotes fail with a repair hint. Misplaced quotes and invalid UTF-8 also fail instead of changing cell values. Doubled literal quotes, multiline CSV fields, and whitespace around quoted fields are supported. Sheet listing verifies CSV/TSV/JSON files are readable; --sheet is only valid for XLSX. XLSX formulas are not executed: results use stored cell values, which may need recalculation in a spreadsheet editor before export.

Confirmation execution also checks the freshly prepared content against the already verified plan immediately before the write/request. Changes between reads fail with OPERATION_PLAN_MISMATCH and produce no write or network call.