Evidrift v0.3.1
Code compiles. APIs drift.
Evidrift v0.3.1 makes the real failure path visible before asking anyone to configure a repository.
Try it
Run the complete PASS-to-FAIL fixture without a global install:
npx --yes evidrift@0.3.1 demoPin it in a repository or CI workflow:
npm install --save-dev evidrift@0.3.1
npx evidrift initNo Evidrift account, API key, cloud backend, package-code execution, or LLM judge is required.
The case this release demonstrates
A dependency changes one declaration from:
parseConfig(input: string, options?: ParseOptions): ParseResultto:
parseConfig(input: string, options: ParseOptions): ParseResultThe existing consumer already passes options, so TypeScript still compiles. Evidrift recomputes the recorded external contract and reports the old signature, current signature, affected line, Receipt ID, and a deterministic FAIL contract_mismatch.
Read the complete, reproduced case: TypeScript compiles, but the dependency signature has drifted.
What changed in v0.3.1
- Added a zero-install, self-contained
evidrift demopath. - Added a real 1200×675 GIF rendered from the captured deterministic CLI transcript.
- Added a static GitHub Pages discovery site, FAQ,
llms.txt, canonical metadata,robots.txt, and sitemap. - Made bare invocation and
evidrift initprint concrete demo, agent, commit, and CI next steps. - Aligned CLI, npm, GitHub, and MCP Registry metadata on
0.3.1.
Verification behavior and the Receipt schema did not change in this release.
Release map
- Changelog for v0.3.1
- npm package:
evidrift@0.3.1 - Complete TypeScript signature-drift case
- Captured CLI transcript
- Live documentation
- MCP Registry package
- Full diff: v0.3.0...v0.3.1
Boundary
Evidrift does not prove runtime correctness or decide whether a dependency change is good. It checks that a deterministic TypeScript or repository-local JSON contract previously recorded for an affected line still matches.
