MapperPlus

05·Remediation

We fix the code for you.

MapperPlus fixes the line that causes the issue and opens a merge request in GitHub, GitLab, or Bitbucket. Your engineers review it and stay on what matters.

Get a DemoAll services

Works with

  • GitHub
  • GitLab
  • Bitbucket
Merge request opened

We fix the line, not the symptom.

The request that proved the finding is traced to the file and the line.The code is changed, and a merge request is opened.

From a finding to a merge request

Three stages run on their own. Your team ships the fourth.

The file is opened, the code is fixed with a note on what it stops, and the change arrives in the review you already run.

  1. 01

    Traced to the file

    Autonomous

    The endpoint is looked up in the repository that owns the behavior. The path and the line.

  2. 02

    The code is fixed

    Autonomous

    MapperPlus writes the fix, with a note on what it stops.

  3. 03

    Merge request opened

    Autonomous

    GitHub, GitLab, or Bitbucket. A branch, a description, and the finding it closes.

  4. 04

    Engineering reviews

    Your team

    The same review as any other patch. Approve and merge, or resolve.

We never ship for you.

Every change arrives as a merge request.Your engineers read it like any other change and decide.

The change

A few lines, written for you.

The coupon branch returned before the charge was captured. The change captures first and rejects the order when nothing was charged. The finding moves to deployed when it ships.

From the acme.com demo workspace. Acme is not a real company.

checkout/capture.ts

+3−1

48 async function capture(order) {
49−if (order.coupon) return fulfill(order)
49+const charged = await gateway.capture(order.total)
50+if (!charged || order.total <= 0) return reject(order)
51+return fulfill(order)
52 }

Fixed by MapperPlus · a coupon can no longer complete checkout without a captured charge.

What it covers

What the fix carries.

  • The exposed endpoint

    The finding stays attached to the request that proved it.

  • The file and the line

    Looked up in the repository that owns the behavior.

  • The fix

    The code is fixed for you and opened in the review you already run.

  • The release

    Your team ships it. The finding moves to deployed when the change is out.

We hand it to your team.

The merge request links the finding, the file, and the pipeline result.Nothing ships without your approval.

What a finding carries

Every field the next team needs.

The merge request, the ticket, and the finding point at the same record, so the review has every field without a lookup.

FindingMP-1842
File
The path in the repository.
Fix
The code change, written for you.
Note
What the change stops from happening.
Review
The host where your team already reviews code.

Next in the path

Alerting
All services

See remediation on your own hosts.

Enter your domain. We map what is exposed and walk you through it in a live demo.

ISO 27001 certifiedNothing to installYour team merges every fix