emfirge_branch_diff
Show the infrastructure diff for an isolated branch compared with its base analysis.
Parameters
branch_id: string · required
{ "branch_id": "branch_456" }
Returns
The response is JSON shaped for the operation. The fields and semantics are described below.
{
"added_nodes": ["NAME_201"], "removed_nodes": [], "modified_nodes": ["NAME_132"], "added_edges": [], "removed_edges": [],
"added_findings": [], "removed_findings": [{ "rule_id": "..." }], "score_before": 72, "score_after": 78, "score_delta": 6,
"newly_internet_reachable": [], "no_longer_internet_reachable": ["NAME_201"]
}
Validation, behavior, and limits
The response contains added_nodes, removed_nodes, modified_nodes, added_edges, removed_edges, added_findings, removed_findings, score_before, score_after, score_delta, newly_internet_reachable, and no_longer_internet_reachable.
Arrays describe modeled node, edge, and finding changes against the immutable base. Scores are 0–100 posture scores where higher is safer; score_delta is evidence about the model, not a deployment guarantee.
Branch changes remain isolated and do not mutate AWS. Re-scan when the live account has changed since the base analysis.