# osmedeus **Repository Path**: mirrors/osmedeus ## Basic Information - **Project Name**: osmedeus - **Description**: Osmedeus 是用于侦察和漏洞扫描的全自动安全工具,可以自动运行工具集,以便针对目标进行侦察和漏洞扫描 - **Primary Language**: Python - **License**: MIT - **Default Branch**: main - **Homepage**: None - **GVP Project**: No ## Statistics - **Stars**: 51 - **Forks**: 20 - **Created**: 2019-07-02 - **Last Updated**: 2026-02-07 ## Categories & Tags **Categories**: security-dev **Tags**: None ## README # Osmedeus

Osmedeus
Osmedeus - A Modern Orchestration Engine for Security

## What is Osmedeus? [Osmedeus](https://www.osmedeus.org) is a security focused declarative orchestration engine that simplifies complex workflow automation into auditable YAML definitions, complete with encrypted data handling, secure credential management, and sandboxed execution. Built for both beginners and experts, it delivers powerful, composable automation without sacrificing the integrity and safety of your infrastructure. ## Features - **Declarative YAML Workflows** - Define reconnaissance pipelines using simple, readable YAML syntax - **Multiple Runners** - Execute on local host, Docker containers, or remote machines via SSH - **Event-Driven Triggers** - Cron scheduling, file watching, and event-based workflow triggers with deduplication and filter functions - **Template Engine** - Powerful variable interpolation with built-in and custom variables - **Utility Functions** - Rich function library with event generation, bulk processing, and JSON operations - **REST API Server** - Manage, trigger, and cancel workflows programmatically - **Distributed Execution** - Scale with Redis-based master-worker pattern for parallel scanning - **Notifications** - Telegram bot and webhook integrations - **Cloud Storage** - S3-compatible storage for artifact management - **LLM Integration** - AI-powered workflow steps with chat completions and embeddings See [Documentation Page](https://docs.osmedeus.org/) for more details. ## Installation ```bash curl -sSL http://www.osmedeus.org/install.sh | bash ``` See [Quickstart](https://docs.osmedeus.org/quickstart/) for quick setup and [Installation](https://docs.osmedeus.org/installation/) for advanced configurations. | CLI Usage | Web UI Assets | Workflow Visualization | |-----------|--------------|-----------------| | ![CLI Usage](https://raw.githubusercontent.com/osmedeus/assets/refs/heads/main/demo-images/cli-run-with-verbose-output.png) | ![Web UI Assets](https://raw.githubusercontent.com/osmedeus/assets/refs/heads/main/demo-images/web-ui-assets.png) | ![Workflow Visualization](https://raw.githubusercontent.com/osmedeus/assets/refs/heads/main/demo-images/web-ui-workflow.png) | ## Quick Start ```bash # Run a module workflow osmedeus run -m recon -t example.com # Run a flow workflow osmedeus run -f general -t example.com # Multiple targets with concurrency osmedeus run -m recon -T targets.txt -c 5 # Dry-run mode (preview) osmedeus run -f general -t example.com --dry-run # Start API server osmedeus serve # List available workflows osmedeus workflow list # Query database tables osmedeus db list --table runs osmedeus db list --table event_logs --search "nuclei" # Evaluate utility functions osmedeus func eval 'log_info("hello")' osmedeus func eval -e 'http_get("https://example.com")' -T targets.txt -c 10 # Platform variables available in eval osmedeus func eval 'log_info("OS: " + PlatformOS + ", Arch: " + PlatformArch)' # Show all usage examples osmedeus --usage-example ``` ## Docker ```bash # Show help docker run --rm j3ssie/osmedeus:latest --help # Run a scan docker run --rm -v $(pwd)/output:/root/workspaces-osmedeus \ j3ssie/osmedeus:latest run -f general -t example.com ``` For more CLI usage and example commands, refer to the [CLI Reference](https://docs.osmedeus.org/getting-started/cli). ## High-Level Architecture ```plaintext ┌───────────────────────────────────────────────────────────────────────────┐ │ OSMEDEUS WORKFLOW ENGINE │ ├───────────────────────────────────────────────────────────────────────────┤ │ ENTRY POINTS │ │ ┌──────────┐ ┌──────────┐ ┌──────────┐ ┌─────────────┐ │ │ │ CLI │ │ REST API │ │Scheduler │ │ Distributed │ │ │ └────┬─────┘ └────┬─────┘ └────┬─────┘ └─────┬───────┘ │ │ └─────────────┴─────────────┴──────────────┘ │ │ │ │ │ ▼ │ │ ┌─────────────────────────────────────────────────────────────────────┐ │ │ │ CONFIG ──▶ PARSER ──▶ EXECUTOR ──▶ STEP DISPATCHER ──▶ RUNNER │ │ │ │ │ │ │ │ │ Step Executors: bash | function | parallel | foreach | remote-bash │ │ │ │ http | llm │ │ │ │ │ │ │ │ │ Runners: HostRunner | DockerRunner | SSHRunner │ │ │ └─────────────────────────────────────────────────────────────────────┘ │ └───────────────────────────────────────────────────────────────────────────┘ ``` For more information about the architecture, refer to the [Architecture Documentation](https://docs.osmedeus.org/architecture). ## Roadmap and Status The high-level ambitious plan for the project, in order: | # | Step | Status | | :-: | ----------------------------------------------------------------------------- | :----: | | 1 | Osmedeus Engine reforged with a next-generation architecture | ✅ | | 2 | Flexible workflows and step types | ✅ | | 3 | Event-driven architectural model and the different trigger event categories | ✅ | | 4 | Beautiful UI for visualize results and workflow diagram | ✅ | | 5 | Rewriting the workflow to adapt to new architecture and syntax | ✅ | | 6 | Testing more utility functions like notifications | ✅ | | 7 | Generate diff reports showing new/removed/unchanged assets between runs. | ❌ | | 8 | Adding step type from cloud provider that can be run via serverless | ❌ | | N | Fancy features (to be discussed later) | ❌ | ## Documentation | Topic | Link | |----------------------|----------------------------------------------------------------------------------------------------------| | Getting Started | [docs.osmedeus.org/getting-started](https://docs.osmedeus.org/getting-started) | | CLI Usage & Examples | [docs.osmedeus.org/getting-started/cli](https://docs.osmedeus.org/getting-started/cli) | | Writing Workflows | [docs.osmedeus.org/workflows/overview](https://docs.osmedeus.org/workflows/overview) | | Event-Driven Triggers| [docs.osmedeus.org/advanced/event-driven](https://docs.osmedeus.org/advanced/event-driven) | | Deployment | [docs.osmedeus.org/deployment](https://docs.osmedeus.org/deployment) | | Architecture | [docs.osmedeus.org/concepts/architecture](https://docs.osmedeus.org/concepts/architecture) | | Development | [docs.osmedeus.org/development](https://docs.osmedeus.org/development) and [HACKING.md](HACKING.md) | | Extending Osmedeus | [docs.osmedeus.org/development/extending-osmedeus](https://docs.osmedeus.org/development/extending-osmedeus) | | Full Documentation | [docs.osmedeus.org](https://docs.osmedeus.org) | ## Disclaimer Osmedeus is designed to execute arbitrary code and commands from user supplied input via CLI, API, and workflow definitions. This flexibility is intentional and central to how the engine operates see [Security Warning](https://docs.osmedeus.org/others/security-warning) page for more details. **Think twice before you:** - Run workflows downloaded from untrusted sources - Execute commands or scans against targets you don't own or have permission to test - Use workflows without reviewing their contents first You are responsible for what you run. Always review workflow YAML files before execution, especially those obtained from third parties. ## License Osmedeus is made with ♥ by [@j3ssie](https://twitter.com/j3ssie) and it is released under the MIT license.