# lpm info (/docs/packages/info)



```bash
lpm info <package[@version]> [--version <V>]
```

Fetches a package's metadata and prints it in a human-readable card: name, description, the chosen version's ecosystem, integrity hash, and full dependency list. With `--json`, returns the raw metadata for tooling.

Routing matches [`lpm install`](/docs/packages/install):

* `@lpm.dev/*` fetches from LPM.dev Registry.
* `@scope/pkg` follows the current project's `.npmrc` `@scope:registry=...` mapping when one exists.
* Unscoped names (`react`, `zod`, `lodash.merge`) use the current project's default `.npmrc` registry, or npmjs.org when no override is present.

If you specifically mean an LPM.dev Registry package, prefer the fully scoped `@lpm.dev/owner.pkg` form. That is the unambiguous spelling.

By default, `lpm info` shows the latest version. Use inline `package@version` or pass `--version <V>` to inspect a specific release.

## Examples [#examples]

```bash
lpm info react                                       # npmjs.org (or project .npmrc default registry)
lpm info react@0.14.3                                # npm-style inline version
lpm info @my-co/internal                             # project .npmrc scoped registry
lpm info @lpm.dev/owner.pkg                          # force LPM.dev Registry
lpm info @lpm.dev/owner.pkg --version 2.1.0          # specific version
lpm info @lpm.dev/owner.pkg --json | jq '.versions' # structured output for tooling
```

## What's shown [#whats-shown]

For the chosen version:

* `version` — the actual semver
* `ecosystem` — `js`, `swift`, etc.
* `integrity` — SRI hash (truncated for display, full in `--json`)
* `dependencies` — declared runtime deps with their ranges

The full registry payload (every version, dist-tags, maintainers, README, etc.) is available via `--json`.

## Flags [#flags]

| Flag            | Effect                                                                                                |
| --------------- | ----------------------------------------------------------------------------------------------------- |
| `--version <V>` | Show a specific version instead of latest. Alternative to inline `package@version`; do not pass both. |

Plus the [global flags](/docs/commands#global-flags) — `--json` returns the full registry record.

## See also [#see-also]

* [`lpm search`](/docs/packages/search) — search npm, custom registries, or LPM.dev Registry depending on the query
* [`lpm quality`](/docs/packages/quality) — quality report
* [`lpm download`](/docs/packages/download) — fetch the tarball without installing