lpm info

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:

• @lpm.dev/* fetches from lpm.dev.
• @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 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

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
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

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

Plus the global flags — --json returns the full registry record.

See also

• lpm search — search npm, custom registries, or lpm.dev depending on the query
• lpm quality — quality report
• lpm download — fetch the tarball without installing