Arbitrary code execution
arbitrary-code-executionThe node can run code or shell commands that were not decided in advance.
Where it sits
1 level deep- execution-risk
- arbitrary-code-execution
Each term is a kind of the one before it. A rule written about any term in this chain also applies to arbitrary-code-execution.
No term is narrower than arbitrary-code-execution.
What it costs
declared on the cardA blueprint starts at a clean 4, loses the weight of every marker present, and the result is clamped into 1–4. arbitrary-code-execution is charged once for the whole blueprint no matter how many nodes carry it. The explanation still lists every node that established it.
Nothing in the topology can establish arbitrary-code-execution on its own, it is a fact about what the node does that only its author can state. The analyzer takes the card at its word and names the node in the explanation.
The number lives in the engine's configuration and not in this vocabulary. A recalibration touches one file, so every blueprint is charged the same way. Nothing records which calibration an evaluation was made under, so move a weight and two evaluations stop being comparable.