What pkgtree does

pkgtree lets you see what a published package actually ships. You paste a package name, version, or registry URL, and the backend fetches the published artifact, safely extracts it, and renders the files exactly as they were shipped — across PyPI, npm, crates.io, and Go.

Alongside the files, each package gets a dependency snapshot: its direct and transitive dependencies, dependents, maintainers, and source repository — pulled from each ecosystem's own data and shown only where it exists. The goal is a fast, neutral view of a package as-is, with no install and no execution.

Two companion views go deeper for npm: a full transitive dependency map with publisher and lifecycle detail (/scan), and a lookup for where a package appears across public GitHub repositories (findmypkg).

This web app is intentionally narrow. It inspects public packages only. There is no local repository upload, no auth, and no saved views.

Power users can point this page at the separate CLI repository by setting NEXT_PUBLIC_CLI_REPO_URL.