What it does
SDKProof addresses a common problem: after a library ships a big release that renames or removes things, AI coding assistants keep writing the old version from memory, and the code no longer compiles. The tool has two halves, both run through npx. The first, npx sdkproof drift, reads two published versions of an npm package and compares their type declarations. It lists functions, hooks and classes that disappeared without being deprecated first. Nothing is installed and no model is called, and the site says no API key is needed. The second, npx sdkproof followed by a package name, gives a model small realistic coding jobs for that package. Each answer goes into a project with the real package installed and through the TypeScript compiler, and an answer passes only if it compiles. No AI judges the result. The site publishes scorecards for eight libraries, built from 102 answers of which 20 did not compile. The site is open about limits: the published scores come from a single model, with one attempt and no documentation, on 10 to 15 tasks per library, and compiling does not prove the code behaves correctly. Library authors can ask for their package to be scored.
Capabilities
- drift command that diffs type declarations between two npm versions
- Compiles model-written code against the real installed package with tsc
- Pass or fail decided by the compiler, with no AI judge
- Public scorecards for eight popular TypeScript libraries
- Open-source code, with scorecards available on request
When to use it
- You maintain a TypeScript package and want to see which removed APIs AI assistants still write
- You want evidence of how current an AI model's knowledge is for a library you depend on
- You are comparing how well AI coding tools handle a recent major release
