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, it returns metadata from the selected registry, plus success and _cache diagnostics.

lpm info checks the registry for current metadata on every run. If the cached response has an ETag, the registry can return HTTP 304.

For HTTP 304, LPM CLI reuses the cached body. Install and resolution commands keep their five-minute metadata cache for speed.

Routing matches lpm 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

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 --verbose info @lpm.dev/owner.pkg                # show cache and revalidation details
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

JSON includes the version metadata that the selected registry returns. npm and custom registries can omit fields such as the README and maintainers.

JSON output also includes _cache diagnostics:

{
  "_cache": {
    "status": "revalidated",
    "age_seconds": 143,
    "network_request": true,
    "not_modified": true
  }
}

Use the global --verbose flag to show the same cache and revalidation information in human output.

Flags

Plus the global flags — --json returns registry metadata plus LPM diagnostics.

See also

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