Protocol teams
Review authorized Solidity components. Keep source fingerprints, findings and revision evidence together.
Explore the workflow ↗Loading page…
Loading page…
Connect technical findings, asset context and review decisions. See the evidence. Understand the boundary. Keep your team in control.
The router links a source assessment to the assets it may affect. Select evidence before deciding what a finding means.
Explore how the pieces fit. The demonstration below is interactive; it does not run an assessment or connect to customer systems.
Run the local Solidity agent on an authorized repository. Keep source local and export findings with explicit coverage.
Local analysis · JSON and HTML reportsExplore assess →Inspect inputs and coverage before interpreting a result.
Explore a sample history of six report revisions. Switch severity or move through the timeline to see how the finding count changes.
A lower count is not a security guarantee. Coverage, confidence and the underlying evidence still matter.
How to compare reports →Inspect a sample coverage matrix. A completed check applies to its stated scope; it does not certify the whole system.
This is an illustrative coverage map, not a report about your repository.
Filter this sample activity log to explore the kind of context a review workflow needs. These entries are examples, not live customer activity.
| Time | Action | Role | Context |
|---|---|---|---|
| 09:14 | Report imported | Analyst | Revision 06 · Source excerpts omitted |
| 09:22 | Finding triaged | Reviewer | Priority recorded · Rationale attached |
| 09:31 | Baseline pinned | Owner | Version retained · Scope documented |
| 09:40 | Case assigned | Owner | Reviewer assigned · Evidence linked |
| 09:52 | Proposal reviewed | Reviewer | Simulated decision · No execution |
5 sample entries shown · No external systems connected
Review authorized Solidity components. Keep source fingerprints, findings and revision evidence together.
Explore the workflow ↗Organize private cases, asset context and reviewer decisions. Make missing coverage part of the conversation.
Explore the workflow ↗Create a repeatable local checkpoint, export reports and bring a reviewable record into the workspace.
Explore the workflow ↗Follow the current workflow from your authorized repository to a private review. Hosted scanning and transaction enforcement remain disabled.
node scanner/cli.mjs scan "C:/path/to/project" --output assessment.jsonUse only repositories you are authorized to assess.
Read the complete guide →No. The charts, network, coverage matrix and activity log on this page use illustrative data. They do not scan, connect to customer systems or make security claims.
No. The current workflow supports local assessments and private report review. Hosted execution remains disabled.
No. Current proposal workflows are observation-only. Signing, sending and transaction enforcement are not connected.
The pricing page describes beta access and planned options. Scope-specific commercial prices have not been announced.