Paramspider
0.1.0Mining URLs from dark corners of Web Archives for bug hunting/fuzzing/further probing.
- Verified 24 Sept 2026
- git c44bdaa
- MIT
- 3.2k stars
Install and run
otlite install paramspiderInstalls
github.com/devanshbatham/ParamSpider at c44bdaainto its own virtualenv. otlite lists what it will install and asks before it starts.otlite run paramspider -- d:example.comType your own value to rewrite the commands. It stays in this page: nothing is sent or saved.
paramspiderreceivesparamspider --domain example.com
No otlite yet? Install it in one line
curl -fsSL https://get.otinstaller.com/otlite | shLinux and macOS, no Docker. It uses your Python and pipx when both are there, and otherwise brings its own Python. About otlite · otlite docs
What it takes
Typed inputs after -- become Paramspider's own arguments. Anything else after -- passes through unchanged, so every option of the tool still works.
| Input | With otlite | paramspider receives |
|---|---|---|
Domaind: | otlite run paramspider -- d:example.com | paramspider --domain example.com |
What a run leaves
Every run is saved under results/ where you run otlite (or --output, or OTLITE_RESULTS_DIR): what the tool printed, a sidecar with how it ran, and an envelope.
results/paramspider/example.com/<time>_paramspider_example.com_<run id>.txtresults/paramspider/example.com/<time>_paramspider_example.com_<run id>.meta.jsonresults/paramspider/example.com/<time>_paramspider_example.com_<run id>.envelope.json
{
"envelope": 1,
"tool": "paramspider@0.1.0",
"runtime": "otlite",
"input": { "target": "example.com" },
"case": null,
"started_at": "…", "ended_at": "…", "duration_ms": …,
"exit_code": 0,
"status": "complete",
"entities": [{ "type": "url", "value": "…" }, …],
"warnings": [],
"output": { "path": "results/paramspider/example.com/<time>_paramspider_example.com_<run id>.txt", "sha256": "…", "bytes": … }
}otlite results --tool paramspiderotlite extract paramspiderotlite diff paramspider example.comList the saved runs, pull out every indicator, or compare the two latest runs against the same target.
With other tools
These run it with every other installed tool that takes the same input, a few at a time, and save each run:
otlite run --all d:example.comotlite auto example.com