[WARP] Add optional `analysis.warp.fetcher` activity to run fetch networked functions as apart of initial analysis

This is off by default for the obvious reasons, we may also in the future want to expand upon this with a "matched view" such that the first step a user can take after loading is to validate what functions were matched and decide if they want to keep any of that data.

This fetch happens as apart of the initial analysis, such that a headless script will not return from the load function until it has finished fetching. We may want to add a configurable timeout, and/or run the fetch out of band (let load return before fetching finishes).

0 files changed, 0 insertions, 0 deletions