Read a versioned OpenAPI document and a consumer usage inventory, and link the deprecated operations to the consumers actually calling them — with the announced removal date and the documented replacement.
This walkthrough uses the tool's public README and checked-in example files. Run the command from a repository checkout with Node.js 22+; inspect the source before using it on your own files.
Run the checked-in example
npm install github:edilec/api-deprecation-scannerRead the result
This installs the public GitHub source; api-deprecation-scanner is not published to npm.
Where this check stops
It cannot conclude that nothing calls an operation. It can conclude that no consumer in the inventory called it during the declared window. A consumer absent from the inventory is unknown, not safe. That is why the coverage block is required, why it is validated as strictly as the usage, and why any shortfall in it is an error that makes the run incomplete rather than a quiet pass.
Before adapting the command to your own workflow, review the accepted inputs, exit codes and safety boundaries in the README.
Compiled with AI assistance from checked-in public documentation and example scripts. Run the example and review the repository's current documentation before relying on its result.