Sigvex
SolanaAnalysis2 min read

Solana Program Overview

The results page for a single Solana program — technical details, risk analysis, per-instruction breakdown, and findings, on one page before you open the full Studio.

Open Program OverviewAll guides
svmsolanaprogramoverview

The Solana Program Overview is where a program analysis lands. It sums up what the engine found — the program’s technical profile, its risk, a per-instruction breakdown, and the findings — on a single page, so you can gauge a program before deciding whether to open it in Studio.

Why it exists

Once a run finishes, most reviewers want the summary, not the decompiler IDE: how risky is this program, and where. This page is that summary, and it’s the default landing place from a Solana analysis run and from an asset card, with a path into Studio when you want to go deeper.

Who uses it

  • Auditor — reviews the risk profile and findings for a specific SVM program.
  • Researcher — opens the program in Studio from the breadcrumb to keep digging.

How to open it

  1. Finish a Solana analysis run — it redirects here on success.
  2. From an asset card for a Solana program.
  3. Direct URL — /solana-program?network=<chain>&address=<base58>.

What’s on the page

A sticky breadcrumb carries the cross-tool actions — Studio, Network, Export, and Share. Below it the page reads top to bottom:

  • Program technical details — binary format, runtime, framework, and program size.
  • Technical and function analysis — a high-level summary and a per-instruction breakdown.
  • Risk analysis — an instruction-complexity-versus-risk view and a security profile.
  • Security findings — the findings list, with the count in the section heading and per-finding detail on open.
  • Program monitor — opt-in monitoring for the program, in place.

Export downloads a report as PDF or JSON; Share copies a link to the overview.

Limits

  • Requires a signed-in account and both a network and a base58 program ID.
  • The risk and function sections populate only when the analysis produced the underlying data — some programs simply don’t yield every metric, so a sparse page is a valid result, not an error.