speckit-version-guard-check

To check locked dependency versions against the npm registry, resolve exact versions from package-lock.json, pnpm-lock.yaml, or yarn.lock, then compare them with live registry data to produce an authoritative locked versus latest status table.

A dependency version guard is a constraints report verifying locked tech stack versions against live registries and known security advisories. You need it before planning implementation phases to prevent relying on outdated or mismatched dependencies.

Audit npm security advisories by checking vulnerability sources for flagged packages within your lockfiles, recording severity levels and patched-in guidance, and writing the known-issue findings into a structured version-guard constraints report.

Yes, speckit-version-guard-check works with yarn.lock and pnpm-lock.yaml across multi-location repositories by resolving exact versions from these lockfiles across repo root, frontend, and backend directories using defined precedence.

Generate compatibility rules by consulting migration documentation for your dependencies and deriving mandatory constraints that ensure downstream implementation steps follow locked-version-safe APIs within a generated version-guard report.

Downstream implementation tasks use outdated dependency versions because they lack a version-guard constraints artifact verifying locked versions against live registries. Running a version guard check prevents planning phases from relying on mismatched dependencies.