sourcemap-check

Checks npm packages for source maps that expose your source code. Zero config, CI-ready.

sourcemap-check v0.1.0 — checking [email protected]

FAIL Found 3 source map file(s) exposing source code:

  dist/index.js.map
  dist/utils.js.map
  dist/helpers.js.map

Why

Source maps (.js.map, .css.map) contain mappings back to your source code — variable names, comments, file structure, and often the full source text via sourcesContent. When you publish an npm package with source maps, anyone who installs it gets access to your unminified code.

Install

npm install -D sourcemap-check

Usage

# Check current project (runs npm pack, inspects, cleans up)
npx sourcemap-check

# Check an existing tarball
npx sourcemap-check ./my-package-1.0.0.tgz

# JSON output for CI
npx sourcemap-check --json

Exit codes

| Code | Meaning | |------|---------| | 0 | No source maps found | | 1 | Source maps detected | | 2 | Tool error |

Add to CI

npm scripts

{
  "scripts": {
    "prepublishOnly": "sourcemap-check"
  }
}

GitHub Actions

- name: Check for source maps
  run: npx sourcemap-check

JSON output

npx sourcemap-check --json

{
  "package": "my-package",
  "version": "1.0.0",
  "files": 47,
  "sourceMaps": [
    "dist/index.js.map",
    "dist/utils.js.map"
  ],
  "passed": false
}

Programmatic API

import { readTarball, findSourceMaps, packProject } from "sourcemap-check";

const tgzPath = await packProject(process.cwd());
const { entries } = await readTarball(tgzPath);
const sourceMaps = findSourceMaps(entries);

if (sourceMaps.length > 0) {
  console.log("Source maps found:", sourceMaps);
}

What it checks

File extensions: .js.map, .css.map, .mjs.map, .cjs.map

That's it.

Requirements

Node.js >= 20

License

MIT