vigiles API reference
    Preparing search index...

    Interface ScriptRunResult

    What a program did: its exit, its output, and (when confined) its effects.

    interface ScriptRunResult {
        egress: readonly EgressAttempt[];
        egressDropped?: { bytes: number; packets: number };
        exitCode: number;
        filesWritten?: readonly string[];
        stderr: string;
        stdout: string;
    }

    Hierarchy (View Summary)

    Index

    Properties

    egress egressDropped? exitCode filesWritten? stderr stdout

    Properties

    egress: readonly EgressAttempt[]

    Network egress the run attempted. With RunScriptOptions.recordEgress: every (blocked) attempt the proxy saw. With RunScriptOptions.egress: the allowlisted hosts actually reached, with packet counts. Empty otherwise.

    egressDropped?: { bytes: number; packets: number }

    Allowlisted-egress mode only: aggregate off-allowlist traffic the packet wall dropped. Undefined when RunScriptOptions.egress was unset.

    exitCode: number

    Exit code. A signal-killed run reports 1.

    filesWritten?: readonly string[]

    Files written to the work dir (relative paths). undefined when writes were never recorded — a different fact from [] ("recorded, wrote nothing"). Recording diffs the work dir before and after, which only a CONFINED run does. assertNoWrite / assertWroteOnly refuse undefined rather than pass having inspected nothing.

    stderr: string

    Everything the program wrote to fd 2. Advisory output usually lives HERE — a runner that reads only stdout silently discards it.

    stdout: string

    Settings

    Member Visibility

    On This Page

    Properties