npm tarball audit 2026

We downloaded the latest published tarball of 331 npm packages, the exact bytes npm install fetches, and inspected every file. Numbers below are recomputed on every crawl (last run 2026-11-19).

46%ship source maps
30%embed full original source
32%over 1 MB unpacked
52%nothing flagged

1. Source maps are the norm

152 of 331 packages (46%) publish .map files, 21K map files in total. 99 (30%) go further and inline sourcesContent, which means the original, pre-build source is sitting in the tarball. For open-source code that's harmless weight. For a closed-source SDK or CLI it's the whole codebase.

2. Tarballs are bigger than they need to be

Median unpacked size is 339.7 KB. 105 packages (32%) exceed 1 MB and 20 exceed 10 MB. Size alone isn't a leak, but it's the usual symptom: maps, tests, fixtures and build leftovers that a files allowlist in package.json would have dropped.

Largest packagesVersionFilesUnpacked
cloudflare-api-js4.35.03694.4 MB
vercel-api-js2.44.04481.1 MB
litellm-api2.21.04470.6 MB
@sentry/api2.12.09440.2 MB
facebook-nodejs-business-sdk26.0.31,38935.7 MB
box-node-sdk10.19.05,26030.4 MB
@larksuiteoapi/node-sdk1.76.0728.9 MB
hud-sdk1.12.46328.7 MB
@earendil-works/pi-coding-agent1.5.21,32423.3 MB
@hubspot/api-client14.1.38,28019.6 MB

3. Stray files and possible credentials

Smaller but real: 3 packages shipped CI config, 2 shipped editor config and 2 shipped test-coverage output. 15 packages (5%) matched a secret pattern or sensitive-file rule. We don't publish which ones or what matched; some are test fixtures, and the rest belong with the maintainer, not on a web page.

Check yours

Every one of these was a build-config default nobody looked at (see the .npmignore trapfor how files git never saw end up in a tarball, and source maps in npm packages for the per-bundler fix). Scan your package free (no login, the same scanner), or fail the publish in CI when something new shows up.

Method: automated heuristic scan of each package's latest public tarball. Sizes are unpacked. Results describe tarball contents, not the security of a package or its maintainers. Per-package results: npm package reports.