Skip to main content

Advanced Submission Workflow

This guide covers advanced submission steps in the full version 2.0 flow.

1. Preflight Check (Step 2.5) and Manage Dependencies​

Step 2.5 of 5 runs a preflight validation before final scan submission.

Step 2.5 preflight validation panel
Figure 1. Step 2.5 Preflight Check with detected settings and dependencies panel.

What preflight does​

Preflight performs four core checks:

  1. Clone / Unpack: gets repository or zip source ready.
  2. Detect framework and root: identifies framework and candidate root paths.
  3. Scan lockfiles / PM: identifies package manager signals.
  4. Parse configs: parses config context and detects dependency state.

Detected outputs include:

  • Framework
  • Project root (subpath)
  • Package manager
  • Dependency inventory and status

These outputs are editable in the UI, so users can correct auto-detection when needed.

Manage dependencies​

  • Manage dependencies opens a modal with dependency rows.
  • Each dependency can be reviewed for source, version, and status.
  • For missing dependencies, users can set action to Install and choose a suggested version.
  • The modal shows an Install plan (preview) so users can review what would be installed.
  • This step is optional, but addressing missing dependencies improves compile success and review quality.
Manage dependencies modal with install plan preview
Figure 2. Manage dependencies interface.

2. Step 4 of 5: Select Files to Audit (Tree View)​

This mode allows users to choose files from an interactive file tree.

Step 4 file selection tree view
Figure 3. Step 4 tree view with directory panel and selectable file list.

Key behavior:

  • Left panel: repository and directory tree.
  • Right panel: files in the selected directory.
  • Search input filters file names.
  • File type filter supports .sol files or All files.
  • Selection is Solidity-focused. Non-.sol files are shown but not selectable.
  • Select all applies to Solidity files in the current directory.
  • User must select at least one file to continue.

3. Step 4 of 5: Provide Files for Security Review (Markdown)​

This mode accepts a markdown scope file to define review targets.

Step 4 markdown scope upload mode
Figure 4. Step 4 markdown upload with preview and examples.

Key behavior:

  • Step title: Step 4 of 5: Provide Files for Security Review.
  • Upload input accepts .md scope files.
  • For multi-repo GitHub flow, users select repository/commit before upload.
  • Uploaded markdown can be previewed in a confirmation modal.
  • Built-in examples can be copied or downloaded as templates.
  • Next is enabled only after valid markdown content is present.

4. Step 4.5 of 5: Build and Tooling (Advanced)​

This optional advanced step allows users to pin runtime and compile behavior.

Available controls:

  • Node version: Auto, 18.x LTS, 20.x LTS, 22.x Current
  • solc version: Auto, 0.8.24, 0.8.23, 0.8.22, 0.8.20
  • Prebuild commands: optional command list, up to 5 entries
Step 4.5 build and tooling controls
Figure 5. Advanced Build and Tooling options for Node, solc, and prebuild commands.

How to use it:

  1. Leave values at Auto for default behavior.
  2. Pin Node and solc when reproducibility is required.
  3. Add prebuild commands when project setup needs explicit preparation.
  4. Keep commands minimal and deterministic.