Struct ValidationEvidenceBody 

#[non_exhaustive]
pub struct ValidationEvidenceBody {
    pub exploitable: ExploitabilityVerdict,
    pub terminal_status: Option<ValidationTerminalStatus>,
    pub flow_verdicts: Option<Vec<FlowVerdict>>,
    pub attack_flows_confirmed: Option<Vec<String>>,
    pub exploit_artifact: Option<ValidationExploitArtifact>,
    pub executed_proof: Option<ValidationExecutedProof>,
    pub source_analysis: Option<ValidationSourceAnalysis>,
    pub per_finding_results: Option<Vec<PerFindingResult>>,
}

Projected content for a VALIDATION_EVIDENCE artifact: the validation agent’s durable proof of exploitability.

Fields (Non-exhaustive)

Non-exhaustive structs could have additional fields added in future. Therefore, non-exhaustive structs cannot be constructed in external crates using the traditional Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.

exploitable: ExploitabilityVerdict

Exploitability verdict. Explicit UNCERTAIN replaces the producer’s tri-state exploitable: true | false | null, so an absent verdict is never confused with a negative one.

terminal_status: Option<ValidationTerminalStatus>

How the validation run ended. Absent when the producer reported a status with no mapping yet: the rest of the body still projects, so one unmapped enum never costs a customer the whole artifact.

flow_verdicts: Option<Vec<FlowVerdict>>

One verdict per attack flow assessed in the bundle.

attack_flows_confirmed: Option<Vec<String>>

Identifiers of attack flows upgraded to Confirmed provenance.

exploit_artifact: Option<ValidationExploitArtifact>

Concrete payload and its observed effect, when validation produced one by sending an HTTP request. Only an HTTP proof projects here. A validation agent that proves exploitability by RUNNING code against the repository projects executedProof, and one that proves it by reading the source projects sourceAnalysis. All three are mutually exclusive: at most one is present.

executed_proof: Option<ValidationExecutedProof>

Proof the agent produced by executing code against the repository under test, with the output that execution produced.

source_analysis: Option<ValidationSourceAnalysis>

Proof the agent produced by reading the repository’s source, with nothing built or run.

per_finding_results: Option<Vec<PerFindingResult>>

Per-finding breakdown for a multi-finding bundle. Absent for a single-finding bundle.

Implementations

impl ValidationEvidenceBody

pub fn exploitable(&self) -> &ExploitabilityVerdict

Exploitability verdict. Explicit UNCERTAIN replaces the producer’s tri-state exploitable: true | false | null, so an absent verdict is never confused with a negative one.

pub fn terminal_status(&self) -> Option<&ValidationTerminalStatus>

How the validation run ended. Absent when the producer reported a status with no mapping yet: the rest of the body still projects, so one unmapped enum never costs a customer the whole artifact.

pub fn flow_verdicts(&self) -> &[FlowVerdict]

One verdict per attack flow assessed in the bundle.

If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .flow_verdicts.is_none().

pub fn attack_flows_confirmed(&self) -> &[String]

Identifiers of attack flows upgraded to Confirmed provenance.

If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .attack_flows_confirmed.is_none().

pub fn exploit_artifact(&self) -> Option<&ValidationExploitArtifact>

Concrete payload and its observed effect, when validation produced one by sending an HTTP request. Only an HTTP proof projects here. A validation agent that proves exploitability by RUNNING code against the repository projects executedProof, and one that proves it by reading the source projects sourceAnalysis. All three are mutually exclusive: at most one is present.

pub fn executed_proof(&self) -> Option<&ValidationExecutedProof>

Proof the agent produced by executing code against the repository under test, with the output that execution produced.

pub fn source_analysis(&self) -> Option<&ValidationSourceAnalysis>

Proof the agent produced by reading the repository’s source, with nothing built or run.

pub fn per_finding_results(&self) -> &[PerFindingResult]

Per-finding breakdown for a multi-finding bundle. Absent for a single-finding bundle.

If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .per_finding_results.is_none().

impl ValidationEvidenceBody

pub fn builder() -> ValidationEvidenceBodyBuilder

Creates a new builder-style object to manufacture ValidationEvidenceBody.

Trait Implementations

impl Clone for ValidationEvidenceBody

fn clone(&self) -> Self

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for ValidationEvidenceBody

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl PartialEq for ValidationEvidenceBody

fn eq(&self, other: &Self) -> bool

Equality operator ==.

fn ne(&self, other: &Rhs) -> bool

Inequality operator !=.

impl StructuralPartialEq for ValidationEvidenceBody