wyreup
inspect

package.json Validate

Lint a Node package.json for shape errors and npm-publish blockers. Catches invalid names, broken semver, mistyped dependency maps, and weird scripts blocks — without bundling the full npm schema. Strict mode also warns on missing description, repository, keywords, license.

Loading…

About package.json Validate

package.json Validate lints a Node package.json for shape errors and npm-publish blockers, catching invalid names, broken semver, mistyped dependency maps, and malformed scripts blocks, each with a clear path and message. It does this without bundling the full npm schema. Strict mode adds warnings for a missing description, repository, keywords, or license, and your file is checked entirely in the browser.

Category
inspect
Input
Accepts: application/json or text/plain.
Output
Outputs: application/json.
Cost
Free, runs in your browser
Memory
low
Privacy: package.json Validate runs entirely on your device. Files you provide never leave your browser — no uploads, no server, no tracking. The page works offline once loaded.

Common uses

  • Catch an invalid package name or bad version string before npm publish fails on you
  • Spot a mistyped dependencies entry (a version range that isn't valid semver) in a fresh package.json
  • Run strict mode to confirm your package has the metadata npm and registries expect before release
  • Validate a generated or scaffolded package.json that your tooling produced
  • Check a monorepo workspace package for the publish blockers that would break CI
  • Review a contributor's package.json edits in a PR without running a publish dry-run

Frequently asked questions

What kinds of problems does it find?

Invalid names, broken semver, mistyped dependency maps, and malformed scripts blocks, reported with the exact path to each issue.

What does strict mode add?

Warnings for missing description, repository, keywords, and license, fields that aren't required to be valid JSON but are expected for a clean publish.

What input does it accept?

A package.json pasted as application/json or plain text. It returns a JSON report of errors and warnings.

Does it upload my package.json?

No. Linting runs in your browser, so your dependency list and scripts stay on your device.

Does it use the full npm schema?

No. It checks the common shape errors and publish blockers directly rather than bundling npm's complete schema, keeping it lightweight.

Keywords

  • npm
  • package.json
  • validate
  • lint
  • node
  • package

Try next

JSON Formatter
inspect

Pretty-print your package.json so reported error paths line up with what you see.
JSON Diff
inspect

Compare two package.json files to see what changed between versions.
OpenAPI Validate
inspect

Lint the OpenAPI spec that ships alongside your package.
Color Palette
inspect

Extract dominant colors from an image as hex codes.
Image Diff
inspect

Pixel-level diff between two images of the same dimensions.
Image Info
inspect

Extract dimensions, format, and metadata from an image.
PDF Info
inspect

Extract page count and metadata from a PDF.
Hash
inspect

Compute SHA-256, SHA-1, or SHA-512 hashes of files.
JSON Formatter
inspect

Parse and pretty-print JSON with configurable indentation.
Extract PDF Tables
export

Extract tabular data from a PDF as JSON or CSV. Works well for simple tables with aligned columns and no merged cells. Complex tables, rotated text, and scanned PDFs (images) will not extract cleanly.
Topic Keywords
text

Pull the topic-bearing nouns and noun phrases out of any text. Answers "what is this about" — not "what words appear most" (try Text Frequency for that). Runs entirely in your browser.