Browser-backed JavaScript collection and semantic analysis tools for reconnaissance workflows.
extractloads one exact HTTP endpoint in Chromium, captures a screenshot, and collects its document, JavaScript files, lazy-loaded chunks, and available source maps.astqueryparses collected JavaScript and TypeScript with Oxc and produces a structured semantic index containing reconstructed HTTP requests, parameters, symbols, and security-relevant findings.
The tools are intentionally separate binaries. extract handles live browser
collection; astquery performs local, read-only analysis over the collected
files.
Both projects use committed lockfiles:
cargo build --locked --release --manifest-path extract/Cargo.toml
cargo build --locked --release --manifest-path astquery/Cargo.tomlThe resulting binaries are:
extract/target/release/extract
astquery/target/release/astquery
Collection is scoped to the complete requested URL. Different paths or query strings on the same hostname are separate analysis targets and should keep separate result histories.
MIT