# lpm quality (/docs/packages/quality)



```bash
lpm quality <package>
```

Fetches the LPM.dev Registry quality report for an `@lpm.dev/*` package and prints it: a score out of 100, a tier label, and a per-check breakdown grouped by category (readme, license, types, tests, maintenance, etc.).

**Scope: `@lpm.dev/*` packages only.** The quality endpoint belongs to LPM.dev Registry; npm-registry packages aren't covered. For broad quality-shaped signals on installed npm packages, [`lpm audit`](/docs/packages/audit) covers vulnerabilities + behavioral analysis.

The same scoring rubric runs locally during [`lpm publish`](/docs/packages/publish) — `lpm quality` lets you preview an already-published package's grade without installing it.

## Examples [#examples]

```bash
lpm quality @lpm.dev/owner.pkg
lpm quality owner.pkg                                           # short form
lpm quality @lpm.dev/owner.pkg --json | jq '.checks[] | select(.passed == false)'
```

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

* **Score** — points out of 100 (color-coded: green ≥80, yellow ≥50, red below)
* **Tier** — human label: `excellent`, `good`, `fair`, or `needs-work`
* **Ecosystem** — `js`, `swift`, etc.
* **Checks** — per-category list with pass/fail icons, label, and points awarded

## Flags [#flags]

`lpm quality` takes no specific flags besides the [global flags](/docs/commands#global-flags). `--json` returns the full report including check IDs, descriptions, and remediation hints.

## See also [#see-also]

* [`lpm publish`](/docs/packages/publish) — runs the same checks before upload (`--check` shows the report only; `--min-score` gates publishing)
* [`lpm info`](/docs/packages/info) — package metadata
* [`lpm audit`](/docs/packages/audit) — installed-package security audit (different system)