JustHandled Labs
// Developer Tools

npm Publish Payload Preflight

Review an npm pack file list for missing runtime output, sensitive files, and payload drift before publish.

What problem does npm Publish Payload Preflight solve?

A package can publish successfully while omitting built runtime files, leaking local configuration, or silently changing its shipped surface.

Use it to

What it returns

A representative input and result

fixture-backed sample
input {"package":{"name":"tiny-kit","version":"1.0.0"},"pack_files":["package.json","dist/index.js"]}
result READY; runtime payload present; new-file information recorded without publishing.

Access and approval boundaries

Known limitations

Questions

Does it change or upload anything?

No. It reads supplied local evidence and writes only to the selected output directory.

Is this an AI judgment?

No. The packaged checker is deterministic and applies documented rules to the supplied input.

What does a ready result mean?

It means no automated finding was produced. The responsible owner still reviews the original source and decides what to do.

How does malformed input behave?

Invalid JSON, duplicate identifiers, missing required arrays, and invalid core values fail closed.

Can I audit the result?

Yes. Every finding carries a stable code, record identifier, severity, source, and message.

npm Publish Payload Preflight keeps proof and approval boundaries visible.

The listing includes the tested package, realistic samples, declared permissions, and known limitations.

Get npm Publish Payload Preflight on Agensi