Krawl tested by Argusic Runner

What the test found

Krawl standalone mode builds and runs: after pip install -r requirements.txt, uvicorn app:app --app-dir src serves HTTP 200 on /dashf/healthz, answers the honeypot with 204 on /, records POST credentials from 198.51.100.77 into SQLite, and the dashboard API shows that IP categorized as attacker.

Install required no root; py-tlsh needed extracted CPython headers. Server launched via uvicorn on port 5003; /dashf/healthz returned 200 with body {"status":"ok"}; honeypot GET / returned 204 and POST /wp-login.php returned 200; attacker 198.51.100.77 was persisted (total_requests 1), categorized attacker with 5 analyzed_metrics keys after the 1-minute analyze-ips job, and was visible in /dashf/api/ip-stats. Dashboard page, static CSS, prometheus metrics, /docs, and banlist export all returned 200. Two pytest-runner test scripts hardcode port 5000 (test_credentials.sh) and exit if not running there, so they cannot be exercised on the custom port. 75-collected pytest run reports 68 passed 7 failed with every failure passing alone; the same-process failures are test-suite isolation bugs, not app defects.

Argusic installed Krawl in 28 minutes and launched it; verification reached Verified running for real. 4 of 4 recorded errors were worked through (see the timeline below).

Ran out of timeall runs of Krawl

This summary is drawn from the agent's recorded report for this run. Every figure traces to the log and recording above; nothing here is authored.