Skip to content
LikelyAILikelyAI

Dependency change intelligence

Know what the upgrade breaks.

LikelyAI diffs the declared types of your dependencies against their newest release, then names the call sites that stop compiling.

TypeScript and Node.js, read-only, on the repositories you pick.

Impact report

Critical

node-fetch 3 removed Response.buffer

Comparing node-fetch 2.7.0 against 3.3.2

37const response = await fetch(invoiceUrl);

38const body = await response.buffer();

39return parseInvoice(body);

3 call sites, 3 files

See the evidence

How it works

  1. 1

    Declared surface

    Diffed between the installed version and the newest release

  2. 2

    Your call sites

    Resolved by the TypeScript checker, not by a text search

  3. 3

    Report or issue

    With the evidence that produced it attached

Example report

Enough evidence to make the call.

The change, the versions it sits between, every call site that reaches it, and what to do. Nothing else.

Critical

node-fetch 2.7.0 to 3.3.2

Export removed

Response.buffer no longer exists

3 call sites in 3 files

  • src/imports/fetch-invoice.ts:38
  • src/jobs/sync-catalogue.ts:112
  • src/lib/http-client.ts:24

Trust boundary

Your code is scanned, not handed over.

  • Read-only source access
  • No model in the detection path
  • No automatic merges
LikelyAI

See what your next upgrade would break.