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.
Start with one command
Section titled “Start with one command”Run Emendant from the root of a repository:
npx emendant scanEmendant reads the repository’s manifests and lockfiles, selects applicable changes from its bundled feed, and structurally matches affected uses. A result is reported only when the feed describes the change and the code can be attributed to that package.
Evidence, 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”The preview matches TypeScript and JavaScript repositories against curated OpenAI Node SDK v5 changes. It understands npm, pnpm, and Yarn projects, including declared workspaces and aliased npm installs. PyPI dependency detection exists, but Python matching and feed coverage are deferred until after the first public release.