DiffersToNpmRegistry

When this happens

• ✓ Instance is in a Highest Semver, Lowest Semver, or Range Only version group
• ✘ Instance is older than highest semver published to the registry

Severity

Not configurable via severity. Registry-update behaviour is controlled by updateGroups. Writing DiffersToNpmRegistry in a severity map fails with InvalidSeverityKey.

Only the update command surfaces this status; fix, lint, and list are unaffected by it.