feat(npm-check-fork): surface deprecated status for package dependencies

[Copilot]

The @rushstack/npm-check-fork library had no mechanism to detect or report when a dependency has been marked deprecated in the npm registry.

Changes

• interfaces/INpmCheckRegistry.ts: Added deprecated?: string to INpmRegistryVersionMetadata (per-version registry field) and INpmRegistryInfo (aggregated result)
• GetLatestFromRegistry.ts: Reads deprecated from the latest stable version's metadata in the registry response and includes it in the returned INpmRegistryInfo
• interfaces/INpmCheckPackageSummary.ts: Added deprecated?: string to expose deprecation status to library consumers
• CreatePackageSummary.ts: Conditionally spreads deprecated into the summary (property is absent rather than undefined for non-deprecated packages)

Example

const state = await NpmCheck({ cwd: '/path/to/project' });

const deprecated = state.packages?.filter(pkg => pkg.deprecated);
for (const pkg of deprecated ?? []) {
  console.warn(`${pkg.moduleName}: ${pkg.deprecated}`);
  // e.g. "request: Please use a native fetch or node-fetch instead"
}

Original prompt

check if any dependencies are deprecated

The user has attached the following file paths as relevant context:

• .github/copilot-instructions.md

Created from VS Code.

---

📍 Connect Copilot coding agent with Jira, Azure Boards or Linear to delegate work to Copilot in one click without leaving your project management tool.