stackscan 2.6.3__tar.gz → 2.7.2__tar.gz

{stackscan-2.6.3 → stackscan-2.7.2}/PKG-INFO

@@ -1,11 +1,11 @@
-Metadata-Version: 2.4
+Metadata-Version: 2.5
 Name: stackscan
-Version: 2.6.3
+Version: 2.7.2
 Summary: Full web stack, infrastructure, DNS, port, subdomain and CVE analyzer.
 Project-URL: Source, https://github.com/reekeer/stackscan
 Project-URL: Issues, https://github.com/reekeer/stackscan/issues
 Author: reekeer team
-Maintainer-email: delewer <del@reekeer.hidden>
+Maintainer: delewer
 License: MIT
 License-File: LICENSE
 Keywords: cli,fingerprinting,osint,stack,tech,wappalyzer
@@ -77,6 +77,26 @@ pip install "stackscan[geo]"   # offline IP geolocation via geoip2 + a MaxMind .
 `nmap` is used for port scans when present; without it a pure-Python scanner is
 used automatically.
 
+### Inside the reekeer shell
+
+stackscan is also a [reekeer](https://github.com/reekeer/reekeer) plugin, mounted
+at `/tools/recon/stackscan` (alias `ss`):
+
+```bash
+reekeer exec /plugins install reekeer/stackscan
+```
+
+Hosted there it drops the banner and the window title and hands the scan back as
+data for reekeer to render in the shell's own tables, so it reads as a command of
+the shell rather than a script being shelled out to. Every flag behaves the same,
+and standalone (`pip`, `uvx stackscan`) is unchanged.
+
+In reekeer's window the scan also gets a form. stackscan says which of its flags
+are worth a control — the targets, the four switches that decide how deep a scan
+goes, and the bounds worth changing when one is too slow — and reekeer draws
+those. The rest are not hidden: the argument line under the form still takes
+anything argparse takes, `--help` included.
+
 ---
 
 ## ✨ Features
@@ -194,6 +214,46 @@ Below are performance benchmarks conducted on two production targets using diffe
 
 ---
 
+## 🛰 Runner mode
+
+`stackscan --runner` turns the scanner into a worker for a StackScan panel: it
+claims jobs (`POST /api/jobs/claim`), fingerprints each target with the normal
+engine, and posts the results back (`POST /api/results`). It needs nothing but
+network access to the panel — no database, no Redis, no shared filesystem.
+
+```bash
+STACKSCAN_BACKEND_URL=https://panel.example STACKSCAN_WORKER_TOKEN=… \
+  stackscan --runner
+```
+
+| Variable | Default | What it is |
+| --- | --- | --- |
+| `STACKSCAN_BACKEND_URL` | `http://localhost:8787` | Panel base URL |
+| `STACKSCAN_WORKER_TOKEN` | — | Shared worker token, sent as `X-Worker-Token` |
+| `STACKSCAN_RUNNER_ID` | `runner-<host>-<pid>` | Stable id for this runner |
+| `STACKSCAN_RUNNER_BATCH` | `5` | Jobs claimed per cycle |
+| `STACKSCAN_RUNNER_IDLE` | `5` | Seconds to wait when the queue is empty |
+| `STACKSCAN_RUNNER` | — | Truthy value selects runner mode without the flag |
+
+Every one has a flag (`--backend`, `--worker-token`, `--runner-id`, `--batch`,
+`--sigdb`, `--user-agent`), and `--once` runs a single claim/scan/report cycle,
+which is what you want in a cron job or a smoke test. The runner profile is
+deliberately lean — DNS, TLS, geo and IP info, no ports, CVEs or brute passes —
+because it is meant for volume rather than depth.
+
+Packaged for it:
+
+```bash
+docker build -t stackscan:latest .
+docker run --rm -e STACKSCAN_BACKEND_URL=http://panel:8787 \
+  -e STACKSCAN_WORKER_TOKEN=… stackscan:latest
+```
+
+Runner mode is refused inside the reekeer shell: it is a loop that runs until it
+is killed, and a shell command that never answers is not a command.
+
+---
+
 ## 🚀 Smart Scan Pipeline
 
 The Smart Scan engine performs multiple analysis stages to collect infrastructure, technology, and security information about the target before generating the final report.
@@ -325,6 +385,8 @@ stackscan/
 │   ├── config/        ← bundled + sourced sigdb loading
 │   ├── data/          ← builtin.sigdb, cve.json.gz, subdomains.txt
 │   ├── render.py      ← the colorized panel report
+│   ├── embed.py       ← findings as data, and the form, for reekeer to draw
+│   ├── runner.py      ← panel worker: claim jobs, scan, report back
 │   ├── scan.py        ← per-target orchestration
 │   └── cli.py         ← argument parsing and entry point
 ├── scripts/           ← build_cve_db.py (NVD → offline dataset)

{stackscan-2.6.3 → stackscan-2.7.2}/README.md

@@ -39,6 +39,26 @@ pip install "stackscan[geo]"   # offline IP geolocation via geoip2 + a MaxMind .
 `nmap` is used for port scans when present; without it a pure-Python scanner is
 used automatically.
 
+### Inside the reekeer shell
+
+stackscan is also a [reekeer](https://github.com/reekeer/reekeer) plugin, mounted
+at `/tools/recon/stackscan` (alias `ss`):
+
+```bash
+reekeer exec /plugins install reekeer/stackscan
+```
+
+Hosted there it drops the banner and the window title and hands the scan back as
+data for reekeer to render in the shell's own tables, so it reads as a command of
+the shell rather than a script being shelled out to. Every flag behaves the same,
+and standalone (`pip`, `uvx stackscan`) is unchanged.
+
+In reekeer's window the scan also gets a form. stackscan says which of its flags
+are worth a control — the targets, the four switches that decide how deep a scan
+goes, and the bounds worth changing when one is too slow — and reekeer draws
+those. The rest are not hidden: the argument line under the form still takes
+anything argparse takes, `--help` included.
+
 ---
 
 ## ✨ Features
@@ -156,6 +176,46 @@ Below are performance benchmarks conducted on two production targets using diffe
 
 ---
 
+## 🛰 Runner mode
+
+`stackscan --runner` turns the scanner into a worker for a StackScan panel: it
+claims jobs (`POST /api/jobs/claim`), fingerprints each target with the normal
+engine, and posts the results back (`POST /api/results`). It needs nothing but
+network access to the panel — no database, no Redis, no shared filesystem.
+
+```bash
+STACKSCAN_BACKEND_URL=https://panel.example STACKSCAN_WORKER_TOKEN=… \
+  stackscan --runner
+```
+
+| Variable | Default | What it is |
+| --- | --- | --- |
+| `STACKSCAN_BACKEND_URL` | `http://localhost:8787` | Panel base URL |
+| `STACKSCAN_WORKER_TOKEN` | — | Shared worker token, sent as `X-Worker-Token` |
+| `STACKSCAN_RUNNER_ID` | `runner-<host>-<pid>` | Stable id for this runner |
+| `STACKSCAN_RUNNER_BATCH` | `5` | Jobs claimed per cycle |
+| `STACKSCAN_RUNNER_IDLE` | `5` | Seconds to wait when the queue is empty |
+| `STACKSCAN_RUNNER` | — | Truthy value selects runner mode without the flag |
+
+Every one has a flag (`--backend`, `--worker-token`, `--runner-id`, `--batch`,
+`--sigdb`, `--user-agent`), and `--once` runs a single claim/scan/report cycle,
+which is what you want in a cron job or a smoke test. The runner profile is
+deliberately lean — DNS, TLS, geo and IP info, no ports, CVEs or brute passes —
+because it is meant for volume rather than depth.
+
+Packaged for it:
+
+```bash
+docker build -t stackscan:latest .
+docker run --rm -e STACKSCAN_BACKEND_URL=http://panel:8787 \
+  -e STACKSCAN_WORKER_TOKEN=… stackscan:latest
+```
+
+Runner mode is refused inside the reekeer shell: it is a loop that runs until it
+is killed, and a shell command that never answers is not a command.
+
+---
+
 ## 🚀 Smart Scan Pipeline
 
 The Smart Scan engine performs multiple analysis stages to collect infrastructure, technology, and security information about the target before generating the final report.
@@ -287,6 +347,8 @@ stackscan/
 │   ├── config/        ← bundled + sourced sigdb loading
 │   ├── data/          ← builtin.sigdb, cve.json.gz, subdomains.txt
 │   ├── render.py      ← the colorized panel report
+│   ├── embed.py       ← findings as data, and the form, for reekeer to draw
+│   ├── runner.py      ← panel worker: claim jobs, scan, report back
 │   ├── scan.py        ← per-target orchestration
 │   └── cli.py         ← argument parsing and entry point
 ├── scripts/           ← build_cve_db.py (NVD → offline dataset)

{stackscan-2.6.3 → stackscan-2.7.2}/pyproject.toml

@@ -14,7 +14,7 @@ authors = [
   { name = "reekeer team" }
 ]
 maintainers = [
-  { name = "delewer", email = "del@reekeer.hidden" }
+  { name = "delewer" }
 ]
 
 dependencies = [
@@ -67,6 +67,20 @@ Issues = "https://github.com/reekeer/stackscan/issues"
 [project.scripts]
 stackscan = "stackscan.cli:main"
 
+# Mounts stackscan inside the reekeer shell as /recon/stackscan.
+#
+# Not `/tools/recon`: a root that holds every plugin distinguishes none of them, so the category is
+# the top-level group.
+#
+# Name, version, description, authors and dependencies are read from [project] above, so nothing is
+# repeated here. No arguments are declared on purpose: stackscan's own argparse keeps ownership of all
+# of them, including `--help` and the `sigdb` subcommand, and reekeer hands it the raw tokens.
+[tool.reekeer]
+group = "/recon"
+entrypoint = "stackscan.cli:main"
+python-root = "src"
+aliases = ["ss"]
+
 [tool.hatch.version]
 path = "src/stackscan/__init__.py"
 

{stackscan-2.6.3 → stackscan-2.7.2}/src/stackscan/__init__.py

@@ -2,4 +2,4 @@ from .core import StackscanSession
 from .utils import normalize_url
 
 __all__ = ["StackscanSession", "__version__", "normalize_url"]
-__version__ = "2.6.3"
+__version__ = "2.7.2"