Sample Assessments
0One illustrative contractLOCAL DEMO · SAMPLE DATA
Security Overview
A clearer view of your contract and a practical next step
Total Findings
—Shown after the sample runsHigh Severity
—Illustrative severity ratingLatest Sample
Not runThis visit only · nothing savedExplore the workflow with a fixed example. This demo runs locally. It does not upload files, fetch links or analyse your code
OFFLINE READYFREE PLANDemo allowance · this visit
02
Scans Remaining
Your next contract review starts here
0 of 2 free scans used
KEEP BUILDING WITH PRO
More Scans For Your Next Release
30 scans every month, with remediation guidance to help you move forward
START AN ASSESSMENT
Bring A Contract Into Focus
Choose A Solidity File, Or Use Our Example
Drag a .sol file here to preview its name
Only the file name is displayed. File contents are never read
A Repository-Based Workflow
Preview how you would supply a contract reference
This field is a local interface preview. The sample below always uses DemoVault.sol
A Deployed-Contract Workflow
Preview a contract address or an Etherscan link
No blockchain connection is made. The sample below always uses DemoVault.sol
DemoVault.solFixed illustrative example · two findings
Opening the example…
YOUR WORKSPACE
Contract Assessments
Your Contract Results, In One Place
Run the example above to review its findings, graph and report
DemoVault.solFixed example · no user code analysed
2 findingsSample complete
SCAN ACTIVITY
Scan History
A timeline of your completed assessments
Your Scan Timeline Starts Here
Completed sample scans appear here during this visit
| Scan / Contract | Completed | Findings | Status | Report |
|---|
This visit only
Sample activity resets when you refresh or reset the demo
ILLUSTRATIVE ASSESSMENT
DemoVault.sol SAMPLE
Two example findings, connected to their source
External Call Before The Balance Update
The example transfers Ether before clearing the sender’s recorded balance. A recipient contract could call back into withdraw() while that balance is still available. Review the order of state changes and external interactions
A Failed Transfer Can Go Unnoticed
The example’s pay() function ignores the boolean returned by a low-level call. If the transfer fails, execution can continue without recording that failure. Define and handle the expected failure path explicitly
CODE + CONTEXT
Follow The Finding
DemoVault.sol
Solidity 0.8.20Highlighting the external call and subsequent balance update
Contract Graph
Simplified sampleSELECTED PATH
External Call Before State Update
The order matters: the recipient can regain control before the recorded balance is cleared
Blue outlines show the selected example path
Guidance for human review. These are fixed examples, not an assessment of a submitted contract. Review and test any changes in the context of your own system