Read a manifest and see what each dependency range actually allows, what the scripts chain into, and which fields are missing or inconsistent.
Waiting for a package.json
Paste the whole file. Nothing is uploaded and no registry is contacted.
The breakdown appears here
Every dependency with what its range really admits, every script with what it chains into, and what the manifest is missing.
No registry is contacted, so this cannot tell you the latest published version of anything, whether a package is deprecated, or whether it has a known vulnerability — those need the network and npm outdated or npm audit. What it reads is the file: what your ranges admit, what your scripts call, and what the manifest does not say.
package.json Inspector runs entirely on your device — nothing is uploaded.
You’re on the Free plan. Compare plans
A manifest is mostly ranges, and a range is harder to read than to write. The single most consequential rule is invisible in the syntax: `^0.3.1` does not mean what `^1.3.1` means. Below 1.0.0 the caret pins the minor version, because semver treats every 0.x release as potentially breaking — so one allows patch releases and the other allows minor ones. That difference accounts for a large share of "it worked yesterday".
Every dependency gets a sentence saying what its range admits, and a looseness marker so the ones that allow anything are visible at a glance. A `*` or a `latest` tag in a dependency list is a build that can change without anybody touching the repository.
The scripts panel shows what calls what, including npm's automatic pre and post wrapping. A `prebuild` script running before `build` is a feature people forget they used, and it is the usual reason a build does something nobody can find in the command.
Findings cover the fields that cause problems by being absent: no licence means all rights reserved by default, so nobody may legally use the package; no `type` means CommonJS whatever your files look like; no `engines` means a version of Node nobody tested. Each says what the default is rather than just that the field is missing.
No registry is queried. This cannot tell you the latest published version of anything, whether a package is deprecated, or whether it has a known vulnerability — those need the network, and this phase deliberately has none.
A caret allows changes that do not modify the leftmost non-zero component — so ^1.2.3 allows up to but not including 2.0.0. A tilde allows patch-level changes: ~1.2.3 allows up to but not including 1.3.0. The caret is npm's default because semver promises minor releases are backwards compatible.
Because the caret pins the leftmost NON-ZERO component. In ^1.3.1 that is the major, so minor releases are allowed. In ^0.3.1 it is the minor, so only patches are. Semver treats 0.x as unstable, and the caret respects that — which is why a 0.x dependency updates far less than people expect.
No. That depends on what the registry has published, which needs the network. What it can tell you is exactly what your range permits, which is the part that does not change.
That the default applies: all rights reserved. Nobody may legally use, copy or distribute the package. For something not intended for publication, `private: true` says so explicitly and removes the question.
No. It is parsed in your browser and never leaves the page, which matters for a private manifest listing internal registry URLs or package names.