StigAnalysisP6RunAnalyzerTask
Properties
Diagnostic artefact: undefined symbols PhASAR handles itself (stdlib/ABI/POSIX).
Actual modules, configurations and endpoint sidecars referenced by the run plan. Preserve each path-to-content association; the plan already records absolute paths.
Automatic per-process budget; changes in available CPU capacity invalidate the task measurement.
Exact P5 rewrite matches used to validate selected rule applications.
Complete current transform/review configuration; validated again before native results can be reused.
P5 final-module transform validation paired with bitcodeRewriteReportFile.
Exact successful run recipes and their original execution records; output bytes are tracked by Gradle.
Optional native diagnostics, retained in task inputs and executed command provenance.
Estimated seconds per source configuration entry and MiB of linked bitcode.
Effective P6 property-to-cascade-layer map. Kept as a task input and checked before execution.
Expected PhASAR identity when an included STIG build produced the analyzer. local is set when the sibling checkout wins; the task then refuses any pinned fallback before launching the analyzer.
When present, reported symbol and postcondition problems fail at this severity threshold.
Conventional generated transform file. P6 refuses to run while any entry is still provisional, so an explicitly unknown model can unblock boundary discovery without silently becoming analysis evidence.
Memory allowance per solver worker in MiB; Linux MemoryMax is this allowance times granted workers.
Cascade layer that supplied maxAllowedRamAndSwapMiB, retained in logs and task inputs for diagnostics.
Cascade layer that supplied the build-wide native analyzer capacity.
Maximum configured sink symbols active in one IDE-XTaint solver execution.
Cascade layer that supplied maxSinksPerSolver, retained as execution provenance.
Complete P5 implementation gaps, independent of the narrower run-plan symbol check.
Executable prepared before the input snapshot, including local PhASAR changes with the same version.
Owning Gradle project path captured during configuration for progress and problem provenance.
Execution records survive failed runs independently of publishable analysis evidence.
Maximum source workers per process; zero uses the available share of build-wide CPU and memory budgets.
Human-friendly stig version tag, passed verbatim to the analyzer via --stig-version for analysis.json.provenance.analyzerVersion. Populated at task-configuration time from the strict packaged com.stigway.gradle.plugin.getStigVersion resolver. Resolution here, not at task action time, keeps the task configuration-cache friendly.
Diagnostic artefact: application symbols PhASAR couldn't resolve.