Sample output -- Pre-Launch Contract Scan
(run against our own test contract, written to contain two known bugs on purpose -- not a real customer's contract)

# Automated Audit Report -- SampleLaunch Token

Contract: a test vault contract
Scan type: automated static analysis (Slither) + centralization pattern scan
Risk score: 47/100

## Executive summary
2 critical findings that should be fixed or explained before launch.
- Critical: 2
- Warning: 0
- Info / gas notes: 3
- Centralization / privileged-control notes: 0

## Findings

### Critical
Reentrancy risk (moves ETH) -- line 13
An external call happens before the contract's own state is updated. A malicious contract on the
other end could call back in and drain funds before the balance is corrected. This is the single
most common cause of real exploited hacks in Solidity history.

Reentrancy risk (moves ETH) -- line 22
Same pattern, a second location.

### Info / minor notes
- Solidity compiler version notice -- the declared compiler version range includes versions with
  known compiler-level issues.
- Low-level call used (x2) -- not a bug by itself, but it bypasses Solidity's automatic
  revert-on-failure and type checking, so the surrounding checks matter more.

## Centralization & privileged-control review
These are not bugs -- they're places where a privileged address (typically the owner/deployer) has
power over the contract or its holders. Automated tools like Slither don't flag these because
nothing is technically broken; they're included here because they're exactly what holders ask about.
No owner-privilege patterns from our checklist (mint/burn/sweep/pause/vesting-override) were detected
in this sample.

## Scope & limitations
This is an automated report: static analysis (Slither, open-source, industry-standard) plus a
pattern-based centralization check. It is not a manual line-by-line review by a human auditor, and
it does not prove the contract is safe. It does not execute the contract, does not check
economic/game-theoretic soundness (tokenomics, oracle design, MEV exposure), and cannot see
off-chain components (front end, admin keys, multisig configuration). Treat this as a fast, honest
first pass worth showing holders alongside (not instead of) disclosing who holds admin/owner keys
and what those keys can do.

Your own report, on your own contract, same day: 29 USDC / 27 EUR. Order via Telegram or email -- see the main page.