-
Notifications
You must be signed in to change notification settings - Fork 2
developer building
Welcome to the build guide! Siyarix uses hatchling as its build system. This document covers building from source, packaging, and deploying. Since this is a growing personal project, the build scripts are designed to be as simple and useful as possible.
Note
If you just want to install and use Siyarix, head over to the main installation guide. This page is primarily for developers helping out with the code!
Siyarix uses hatchling for the build process.
[build-system]
requires = ["hatchling>=1.21.1"]
build-backend = "hatchling.build"Building the source code is straightforward:
# Install the build tool
pip install build
# Run the build process
python -m build
# 🎯 Your artifacts will be ready in the dist/ folder:
# dist/siyarix-1.0.0-py3-none-any.whl
# dist/siyarix-1.0.0.tar.gzTip
Development Installation If you are actively developing Siyarix, install it in editable mode:
pip install -e ".[all,cli,siem,dev]"If you're a maintainer publishing a release:
pip install twine
python -m build
# ⚠️ Always test your release on TestPyPI first!
twine upload --repository testpypi dist/*
# ✅ Once verified, push to production
twine upload dist/*You can install specific "extras" depending on what you need.
| Extra | What it provides |
|---|---|
terminal |
UI dependencies like Rich, prompt_toolkit |
cli |
Typer, Rich, prompt_toolkit |
siem |
httpx for SIEM integrations |
autonomous |
Anthropic, Google Generative AI, and OpenAI SDKs |
api |
FastAPI and Uvicorn |
security |
Bandit, Safety, pip-audit |
all |
🌟 All extras combined |
dev |
Pytest, ruff, mypy, pre-commit, build, twine |
pip install "siyarix[autonomous]"
pip install "siyarix[all]"
pip install "siyarix[dev]"A quick look at the directory layout:
siyarix/
├── src/siyarix/ # Package source
├── tests/ # Test suite
├── packages/ # Platform-specific packaging
├── docs/ # Documentation (Built with MkDocs)
├── scripts/ # Utility scripts
├── Dockerfile # Docker build
└── pyproject.toml # Build configuration & metadata
Here's how to install Siyarix:
pip install siyarix
pip install "siyarix[all]"I've also included a Dockerfile if you prefer containers.
# Build the image
docker build -t siyarix:latest .
# Run a quick command
docker run siyarix:latest scan --helpI use GitHub Actions to automate testing and checks on PRs:
- Tests across Python 3.11+
- CodeQL analysis
- Dependabot for dependency updates
I've wrapped common operations in a Makefile:
| Target | Description |
|---|---|
make install |
Install dependencies |
make install-dev |
Install all development dependencies |
make test |
Run the test suite |
make lint |
Run Ruff linter |
make typecheck |
Run MyPy |
make build |
Build the sdist and wheel |
make docs |
Build the documentation |
Caution
Always try to run make test, make lint, and make typecheck before pushing code.
Before shipping a new release:
- Update version in
pyproject.toml. - Document changes in
CHANGELOG.md. - Run tests:
pytest - Lint:
ruff check src/ - Verify types:
mypy src/siyarix/ - Build artifacts:
python -m build - Upload to PyPI via twine.
- Tag the release.
Note
👋 Welcome to Siyarix! This is a personal passion project built by a single developer. It's currently under active development and growing fast. Expect rough edges, but lots of love! ❤️
Welcome to the Siyarix Documentation Map! This page serves as your master compass for navigating the extensive documentation we have built for the platform.
Whether you are a brand new user, a seasoned security operator, or a developer looking to contribute to the core engine, you can find exactly what you need here.
Not sure where to start? Pick the path that best describes you:
Just getting started? We highly recommend following these guides in order:
- Installation Guide — Get Siyarix running on your machine.
- Onboarding Wizard — Let our interactive wizard help you set up your API keys and environment.
- Setup & Configuration — A deeper dive into customizing your setup.
- Your First Run — A gentle walkthrough of your very first Siyarix command.
Ready to put Siyarix to work? Dive into our operational guides:
- Interactive Chat (REPL) — Learn how to use the powerful interactive terminal.
- Security Workflows — Best practices for recon, vulnerability assessment, and incident response.
- Cloud & IaC Scanning — How to secure your cloud environments and infrastructure code.
- Compliance Frameworks — Map your scans to SOC 2, HIPAA, ISO 27001, and more.
Looking under the hood or wanting to write some code? Start here:
- Contribution Guide — Our workflow, standards, and how you can help!
- Codebase Overview — A comprehensive map of our 82+ source modules.
- Testing Standards — How we ensure reliability with pytest and CI/CD.
- Module Architecture — Component design and responsibilities.
If you prefer to browse the raw structure, here is a complete layout of the docs/ folder:
docs/
├── 🚀 getting-started/ # Installation, onboarding, and configuration
│ ├── installation.md # Multi-platform install (pip, brew, winget, docker)
│ ├── onboarding.md # The interactive 11-step setup wizard
│ ├── setup.md # Managing API keys, credentials, and settings
│ ├── first-run.md # A walkthrough of your first session
│ ├── configuration.md # A deep-dive into advanced settings
│ └── troubleshooting.md # Common issues and how to fix them instantly
│
├── 📖 user/ # Daily operations and workflows
│ ├── cli-commands.md # Reference for 50+ CLI commands across 12 groups
│ ├── interactive-chat.md # Mastering the AI REPL and 54+ slash commands
│ ├── security-workflows.md # Recon, vulnerability assessment, incident response
│ ├── cloud-scanning.md # Multi-cloud security scanning (under development)
│ ├── compliance.md # Framework mapping (SOC 2, NIST, GDPR, PCI-DSS)
│ ├── threat-intelligence.md# Integrations with OTX, NVD, and MITRE ATT&CK
│ ├── playbooks.md # Building automated YAML-based IR playbooks
│ ├── workflow-files.md # DAG workflow reference (programmatic API)
│ ├── reporting.md # Multi-format report generation
│ ├── offline-registry.md # Running without AI (Offline/Registry execution mode)
│ └── ai-workflows.md # Advanced AI-driven autonomous operations
│
├── 💻 developer/ # Building, testing, and extending Siyarix
│ ├── codebase-overview.md # Full module structure mapping
│ ├── contribution-guide.md # How to submit PRs and our coding standards
│ ├── module-architecture.md# Component design and responsibilities
│ ├── testing.md # Writing tests (pytest), coverage, and CI/CD
│ └── building.md # Packaging, distribution, and Docker builds
│
├── 🏗️ architecture/ # System design and core internals
│ ├── overview.md # High-level data flow and layered orchestration
│ ├── ai-agent-pipeline.md # The AgentCore reasoning and execution pipeline
│ ├── provider-abstraction.md# How we unify 26 different AI providers
│ ├── execution-engine.md # Plan-based step orchestration
│ ├── memory-and-state.md # Knowledge graph, session persistence, and learning
│ ├── security-model.md # The Permission Gate, DLP, audit logging, and OPSEC
│ └── intent-routing.md # Semantic intent classification and routing
│
├── 🧠 ai/ # Deep dive into the AI provider & agent systems
│ ├── routing.md # Managing 26 providers, failovers, and circuit breakers
│ ├── persona-system.md # Overview of our 10 security personas
│ ├── agent-reasoning.md # The Observe-Reason-Act loop and tool call repair
│ ├── tool-execution.md # The tool registry, capability graph, and parsers
│ ├── ensemble.md # Parallel LLM voting strategies
│ ├── multi-wave.md # Iterative goal execution with context carry-over
│ ├── prompt-architecture.md# System prompt design and management
│ └── safety.md # Our rigorous 8-layer hallucination mitigation system
│
├── 🛡️ security/ # Safety, ethics, and threat models
│ ├── reporting.md # How to safely report vulnerabilities to us
│ ├── threat-model.md # System threat model and our mitigations
│ ├── operational-security.md# TOR routing, stealth modes, and OPSEC controls
│ ├── ethical-policy.md # Mandatory rules of engagement for all users
│ └── abuse-prevention.md # How we prevent misuse of the AI engine
│
└── ⚖️ legal/ # Licensing and governance
├── agpl-guide.md # A plain-English overview of the AGPL-3.0-or-later license
├── why-agpl.md # The philosophy behind our license choice
├── trademark-policy.md # Branding and trademark guidelines
├── responsible-ai.md # Our framework for ethical AI usage
├── disclaimer.md # Important legal disclaimers
└── plugin-exception.md # The license exception for building custom plugins
As you read through the documentation, you might encounter some specific terms. Here is a quick cheat sheet:
| Term | What It Means |
|---|---|
| Provider | The backend AI engine powering Siyarix (e.g., OpenAI, Anthropic, Ollama). |
| Tool | A traditional security executable installed on your system (e.g., nmap, nuclei). |
| Plan | A step-by-step sequence of tool commands intelligently generated by the AI. |
| Workflow | A hardcoded, predefined execution path (usually defined in YAML/JSON) that doesn't require AI generation. |
| Persona | A specialized behavioral profile given to the AI (e.g., instructing it to act specifically as a "Network Recon Specialist"). |
| Knowledge Graph | Siyarix's internal memory where it stores findings (like IP addresses, open ports) to contextually inform future steps. |
Need help finding something specific? Feel free to use the search bar at the top of the documentation site, or open a discussion on our GitHub!