Skip to content

Demo // inside a run

One bug. Five layers.

SAMPLE CODE · SIMULATED

What you just watched

Every layer
is a gate.

One sample for each kind of bug Mallace proves and fixes: SQL injection, command injection, code injection and unsafe deserialization, in Ruby, Python, JavaScript and PHP. Each matches a rule Mallace ships today. The code is sample code. The five layers are the steps every real fix goes through, in order. A finding that fails a gate stops there.

  1. 01

    Scan

    A pinned, offline Semgrep ruleset follows caller input (the amber source) to a dangerous sink (the red line): SQL, shells, eval or unsafe deserialization. Scanning is free and unlimited.

  2. 02

    Prove

    Mallace writes a regression test for the finding and runs it in a sandbox with no network. It has to fail on your current code, or Mallace leaves the code alone.

  3. 03

    Fix

    It writes the smallest change it can. The same test has to pass, and your code still has to compile.

  4. 04

    Review

    A second, independent model reviews the fix. A rejected fix goes back with the reviewer’s feedback, as in the command-injection sample.

  5. 05

    Pull request

    One pull request per verified fix, with the test that proved the bug and a plain-English explanation. Nothing merges automatically.

Also on every scan

Reported,
not rewritten.

Some problems have no code fix to prove. Mallace lists these after the code findings so you can act on them: rotate the key, upgrade the package, change the server setting.

Run it on your own repository.

Scans are free and unlimited. The Free plan includes proved fixes on one repository.