Public Sample · Run on a real app

This is the report
we hand you.
Read every word.

No login. No email wall. We pointed our full security review at OWASP Juice Shop — a real, intentionally-vulnerable app — and published exactly what a client receives. Judge our work before you ever talk to us.

Explore the live dashboard Open the full report →
Real findings, real code 75 copy-paste fixes Nothing redacted
Scroll
11.8/100
Critical

A scanner gives you a number.
We tell you what it means.

The score is just the doorway. Behind it: an app one request away from server takeover — every risk explained in plain business language and traced to the exact line of code.

16
critical & high-severity
in production code
3
paths to full
compromise
75
ready-to-paste
fixes

Not a wall of alerts.
The three that could end the business.

We rank by what actually matters — business impact — so a founder knows where to look first, without reading a single line of code.

Risk 01

Server takeover

routes/b2bOrder.ts:23

A crafted order request runs attacker code on your server — arbitrary code execution, full control.

Risk 02

Code-injection

routes/captcha.ts:22

User input is evaluated as code, letting an attacker inject and run their own logic inside your app.

Risk 03

Stolen credentials

lib/insecurity.ts:23

A secret embedded in the code grants direct access — anyone who reads it walks straight in.

Scanners see syntax.
We follow the data.

A real finding from this report. The automated rule flagged the obvious eval() calls — and walked right past the one that actually owns your server.

Automated scanner MISSED IT
// flagged the literal eval()s…
userProfile.ts:61  eval()   → noted
captcha.ts:22      eval()   → noted

// …but stopped at the alias.
b2bOrder.ts:23     safeEval(...)  → ignored
  the real server-takeover sink
Vollos Lens CAUGHT IT
req.body.orderLinesData
   │ user-controlled input
   ▼
vm.createContext(sandbox)
vm.runInContext(
  'safeEval(orderLinesData)')
   │ 'notevil' pkg — known escapesremote code execution

We traced user input through an aliased import inside a vm context — a sink a rule-based scanner can't follow. That's the difference you're paying for: judgment, not noise.

Every finding ships
with its own fix.

Most reports stop at the bad news. Ours bundles 75 ready-to-paste prompts — drop one into Claude or Cursor and the fix writes itself, grounded in your exact code. You close the loop the same day.

A real one, straight from this report →

F01 · unsafe-eval-sandbox-escape ⧉ copy
# Fix-Ready Prompt · CWE-94 · Critical

Remediate the RCE at routes/b2bOrder.ts:23.

Replace the safeEval / vm block (lines 19–23)
with JSON.parse(orderLinesData) inside a
try/catch and a strict size limit. Validate the
result against an ajv schema. Drop the
'notevil' + 'vm' dependency — neither is a real
sandbox.

# grounded in your file · verified unique anchor

One download.
Everything you need to act.

The styled report

Cover-to-cover PDF — executive summary, top risks, full findings, action plan. Built to forward to your board.

Interactive dashboard

A self-contained page you click through — filter, sort, and inspect every finding live in your browser.

75 fix-prompts

One grounded, copy-paste prompt per finding. Paste into your AI coding tool and ship the fix.

SARIF + JSON

Machine-readable results that drop straight into GitHub code-scanning and your CI pipeline.

Incident-response plan

If something is already exposed, a clear step-by-step so you're not improvising under pressure.

Action plan (30/60/90)

Findings sorted into a phased plan — what to fix today, this sprint, and this quarter. No guesswork on where to start.

Download the full bundle (.zip) ↓

Everything above — report, dashboard, all 75 fix-prompts, SARIF & JSON. Nothing held back.

We published the whole report — every risk, every fix, even the flaws other tools walk past — because the work should sell itself.

This is a public practice app, not a client. No real customer data appears here.

Now point it
at your code.

You just read what we'd hand you. Same depth, same fixes — on your codebase, in days, not weeks.

Flat-rate security review · fixed price, no hourly meter · read-only access