deprecation-scan

Scanning locally scraped documentation cross-references removal notices against your codebase imports to identify deprecated APIs. The resulting structured report cites affected sources, groups findings by severity, and suggests replacements for deprecated APIs still in use.

Auditing Python dependencies for removal notices involves cross-referencing local documentation with the codebase. The process filters findings by the project's minimum Python version and active imports, producing a source-cited report with actionable remediation steps for dependency health workflows.

You can scope deprecation reporting to specific documentation collections using the dependency map. This focuses the analysis on relevant subsets of your locally scraped docs, ensuring the report only highlights deprecated APIs relevant to the selected collection's imports.

The deprecation scan filters results based on the project's minimum Python version. By cross-referencing removal notices with your codebase, it ensures the report only includes deprecated APIs and version-specific warnings relevant to your active environment.

Cross-referencing documentation with your codebase isolates deprecated APIs you actively use from general removal notices. This prevents alert fatigue by producing a focused report with suggested replacements and severity levels tailored to your project's actual imports.