Practical Notes
- GitHub: 6,232 stars · 982 forks; pushed 2026-05-11 (verified via GitHub API).
- README installation uses a one-line install script and includes
--dry-runto preview workflow execution. - CLI examples show modules/flows, concurrency flags, and a built-in API server (
osmedeus serve).
Main
Safety-first usage:
- Treat Osmedeus as an internal security automation runner. Keep targets in a scoped allowlist (your domains, your staging, your owned IPs).
- Start with
--dry-runand inspect what will execute, then run with conservative concurrency. - Keep outputs in a dedicated workspace and store the final report artifacts alongside the run configuration so audits are easy.
If you want to involve an AI agent, have it produce a plan and a safe target list first; never let the agent free-run on the public internet.
FAQ
Q: Is it legal to scan random sites? A: No. Use it only for systems you own or have explicit permission to test.
Q: How do I reduce risk?
A: Use --dry-run, keep concurrency low, and run inside isolated environments.
Q: Can it expose an API?
A: Yes—README includes osmedeus serve to start an API server.