Local by default
A scan runs on your machine. It does not upload source code, execute repository code, or write to the repository.
APIs change.
Your code adapts.
Find the exact TypeScript and JavaScript call sites affected by a known SDK change, locally, precisely, and with the source behind every result.
Install and scan
Section titled “Install and scan”Emendant is published on npm. Run it from the root of a repository with Node.js 20 or later:
npx emendant scanTo add the tool to your project:
npm install --save-dev emendantEvidence, not guesses
Every finding links to a curated change entry and, where needed, carries a trace back to the package import.
Built for CI
Stable JSON output and explicit exit codes let a pipeline distinguish a clean scan, findings, and a tool error.
Find what you need
Section titled “Find what you need”Run your first scanRequirements, first command, and what happens next.
Understand a findingPlacements, severity, warnings, and why a result appeared.
Add Emendant to CIUse exit codes and JSON output safely in automation.
Review securityWhat scan reads, what it never does, and where your source stays.
Current coverage
Section titled “Current coverage”Emendant covers selected changes in six AI SDKs for TypeScript and JavaScript projects.
Run emendant feed update to get newer coverage.