← All steps
Step 03

Impact

Not a vague alert — the exact files that need attention.

split view — broken vs Versionly

src/billing.ts

Your code now
12export async function charge(id: string) {
13  return stripe.paymentIntents.confirm(id, {
14    api_key: process.env.STRIPE_KEY,
15  })
16}

src/billing.ts

Versionly suggests
12export async function charge(id: string) {
13  return stripe.paymentIntents.confirm(id, {
14    stripeAccount: process.env.STRIPE_KEY,
15  })
16}

In one sentence

We find where your code would break.

You control

When a scan runs.

For everyone

Instead of a developer hunting through the whole codebase, Versionly points at the spots that use the changed API.

For engineers

A scan maps call sites and reports the files and symbols affected by the vendor change.

What happens

  1. A scan runs when you ask, or on push if your plan allows it.
  2. You see which files and lines are involved.
  3. Nothing in GitHub is changed at this step.
← DetectReview →