// the take
pacote is npm's internal library for resolving and fetching anything npm can install — registry packages, git repos, tarball URLs, local directories — down to a manifest, packument, or extracted folder. It's the engine behind `npm install` itself, useful if you're building tooling that needs npm-compatible package resolution without shelling out to the npm CLI.
One API surface handles every spec type (semver range, git, github shorthand, tarball URL, local path) instead of forcing callers to branch on spec kind. Extracted file mode/ownership handling (umask, fmode/dmode, root uid/gid normalization) solves a real and easy-to-get-wrong problem with tarball extraction on Unix. Built-in support for verifying npm registry signatures and Sigstore attestations via TUF key material. Caching is pluggable at the packument level (shared Map across calls) so bulk operations avoid redundant registry round-trips.
This specific repo is explicitly marked 'moved' — it's a stale pointer, not the actively maintained location, so anyone landing here via search risks depending on a dead mirror instead of the real thing. It's an internal npm CLI dependency first, public library second: options are passed straight through to npm-registry-fetch and cacache, so using it well means understanding npm's own config surface, not a clean standalone API. Config (registry auth, proxy settings, etc.) assumes an npm-like config object rather than simple constructor options, which is extra friction for non-npm consumers. `prepare`/`prepack` script execution for git and directory specs means pulling a package can run arbitrary code from that package — fine inside npm's trust model, a real supply-chain consideration if you're embedding this in something else.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →