stryx-cli 0.1.0__tar.gz → 0.1.2__tar.gz

{stryx_cli-0.1.0 → stryx_cli-0.1.2}/CODE_OF_CONDUCT.md

@@ -1,101 +1,101 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-We as members, contributors, and leaders pledge to make participation in our
-community a harassment-free experience for everyone, regardless of age, body
-size, visible or invisible disability, ethnicity, sex characteristics, gender
-identity and expression, level of experience, education, socio-economic status,
-nationality, personal appearance, race, religion, or sexual identity
-and orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to a positive environment:
-
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
-
-Examples of unacceptable behavior:
-
-* The use of sexualized language or imagery, and sexual attention or advances of any kind
-* Trolling, insulting or derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a professional setting
-
-## Enforcement Responsibilities
-
-Community leaders are responsible for clarifying and enforcing our standards of
-acceptable behavior and will take appropriate and fair corrective action in
-response to any behavior that they deem inappropriate, threatening, offensive,
-or harmful.
-
-## Scope
-
-This Code of Conduct applies within all community spaces, and also applies when
-an individual is officially representing the community in public spaces.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by opening a GitHub issue tagged `conduct` on the
-[medusa-Security/stryx](https://github.com/medusa-Security/stryx/issues) repository.
-
-All complaints will be reviewed and investigated promptly and fairly.
-
-## Enforcement Guidelines
-
-Community leaders will follow these Community Impact Guidelines in determining
-the consequences for any action they deem in violation of this Code of Conduct:
-
-### 1. Correction
-
-**Community Impact**: Use of inappropriate language or other behavior deemed
-unprofessional or unwelcome in the community.
-
-**Consequence**: A private, written warning from community leaders, providing
-clarity around the nature of the violation and an explanation of why the
-behavior was inappropriate.
-
-### 2. Warning
-
-**Community Impact**: A violation through a single incident or series
-of actions.
-
-**Consequence**: A warning with consequences for continued behavior. No
-interaction with the people involved, including unsolicited interaction with
-those enforcing the Code of Conduct, for a specified period of time.
-
-### 3. Temporary Ban
-
-**Community Impact**: A serious violation of community standards, including
-sustained inappropriate behavior.
-
-**Consequence**: A temporary ban from any sort of interaction or public
-communication with the community for a specified period of time.
-
-### 4. Permanent Ban
-
-**Community Impact**: Demonstrating a pattern of violation of community
-standards, including sustained inappropriate behavior, harassment of an
-individual, or aggression toward or disparagement of classes of individuals.
-
-**Consequence**: A permanent ban from any sort of public interaction within
-the community.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage],
-version 2.1, available at
-[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
-
-Community Impact Guidelines were inspired by
-[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
-
-[homepage]: https://www.contributor-covenant.org
-[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
-[Mozilla CoC]: https://github.com/mozilla/diversity
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior:
+
+* The use of sexualized language or imagery, and sexual attention or advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by opening a GitHub issue tagged `conduct` on the
+[Medusa-Security/stryx](https://github.com/Medusa-Security/stryx/issues) repository.
+
+All complaints will be reviewed and investigated promptly and fairly.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity

{stryx_cli-0.1.0 → stryx_cli-0.1.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: stryx-cli
-Version: 0.1.0
+Version: 0.1.2
 Summary: AI-Powered Dynamic Application Security Testing (DAST) -- part of the MEDUSA security platform
 Author-email: Akhilesh Varma <akhverm@gmail.com>
 License: Apache-2.0
@@ -91,7 +91,7 @@ CLI -> Configuration -> Attack Orchestrator -> { Endpoint Discovery }
 pip install stryx
 
 # From source
-git clone https://github.com/medusa-Security/stryx.git
+git clone https://github.com/Medusa-Security/stryx.git
 cd stryx
 pip install -e .
 ```

{stryx_cli-0.1.0 → stryx_cli-0.1.2}/README.md

@@ -1,184 +1,184 @@
-# STRYX
-
-**AI-Powered Dynamic Application Security Testing (DAST)**
-
-[![License](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](LICENSE)
-[![Python Version](https://img.shields.io/badge/python-3.11+-blue.svg)](https://www.python.org/downloads/)
-[![Build Status](https://github.com/medusa-Security/stryx/actions/workflows/ci.yml/badge.svg)](https://github.com/medusa-Security/stryx/actions)
-
-STRYX is a developer-first, AI-assisted DAST engine that crawls, maps, and tests the live attack surface of web applications. It discovers hidden endpoints, simulates real attacker behavior, and detects exploitable vulnerabilities with minimal false positives. Every finding carries full evidence (request, response, status code, payload, confidence score) -- no heuristic-only results.
-
-**Design philosophy: high signal, low noise.**
-
-## How It Fits Into MEDUSA
-
-- **Remy** -- SAST, analyzes source code pre-deployment.
-- **STRYX** -- DAST, validates a running application's live attack surface and exploitability.
-- **MEDUSA** -- Aggregates findings from both, correlates static and runtime issues, estimates business impact, provides centralized security management.
-
-## Architecture
-
-```
-CLI -> Configuration -> Attack Orchestrator -> { Endpoint Discovery }
-                                                        |
-                                         Authentication Engine
-                                         Authorization Engine
-                                         Injection Engine
-                                         API Fuzzer
-                                         AI Attack Planner
-                                         Evidence Collector
-                                         Report Generator
-                                                        |
-                                              Target Application
-```
-
-## Installation
-
-```bash
-# From PyPI
-pip install stryx
-
-# From source
-git clone https://github.com/medusa-Security/stryx.git
-cd stryx
-pip install -e .
-```
-
-## Quickstart
-
-```bash
-# Run a full scan
-stryx scan http://localhost:8000
-
-# Output:
-# STRYX Scan Results
-# Target: http://localhost:8000
-# Total Findings: 3
-# Breakdown: CRITICAL: 1 | HIGH: 1 | MEDIUM: 1
-```
-
-## Core Modules
-
-| Module | Purpose |
-|--------|---------|
-| Endpoint Discovery | Crawls targets, extracts APIs from OpenAPI/Swagger, sitemaps, JS files, GraphQL |
-| Authentication Scanner | Tests missing auth, weak JWTs, session fixation, cookie security |
-| Authorization Scanner | Tests IDOR, privilege escalation, admin access, multi-tenant escape |
-| Injection Engine | SQL, NoSQL, command, SSRF, path traversal, XXE, SSTI, LDAP injection |
-| API Fuzzer | Parameter mutation, boundary values, type confusion, nested JSON |
-| CORS Scanner | Detects misconfigured CORS policies and origin reflection |
-| GraphQL Scanner | Tests introspection exposure, query depth limiting |
-| AI Attack Planner | Constructs multi-step attack chains across findings |
-| Evidence Engine | Enforces evidence requirements on every finding |
-
-## CLI Reference
-
-### Commands
-
-| Command | Description |
-|---------|-------------|
-| `stryx scan <url>` | Run full security scan |
-| `stryx crawl <url>` | Crawl and discover endpoints |
-| `stryx auth <url>` | Run authentication tests |
-| `stryx fuzz <url>` | Run API fuzzing tests |
-| `stryx report <url>` | Generate reports |
-| `stryx config` | View/update configuration |
-| `stryx providers` | List supported AI providers |
-| `stryx update` | Update STRYX |
-
-### Flags
-
-| Flag | Description |
-|------|-------------|
-| `--deep` | Enable deep scanning |
-| `--json <file>` | Output JSON report |
-| `--html <file>` | Output HTML report |
-| `--markdown <file>` | Output Markdown report |
-| `--threads <n>` | Concurrent threads (1-200) |
-| `--timeout <s>` | HTTP timeout in seconds |
-| `--headers <json>` | Custom headers |
-| `--cookies <str>` | Authentication cookies |
-| `--proxy <url>` | HTTP proxy |
-| `--wordlist <file>` | Custom wordlist |
-| `--rate <n>` | Requests per second limit |
-
-## Configuration
-
-```yaml
-provider: groq
-model: llama-3.3-70b-versatile
-threads: 20
-timeout: 10
-crawl_depth: 5
-respect_robots: false
-ai_attack_planning: true
-modules:
-  auth: true
-  authorization: true
-  injection: true
-  fuzzing: true
-```
-
-Supported AI providers: Groq, OpenAI, Anthropic, OpenRouter, Ollama, XAI, NVIDIA NIM.
-
-## Sample Report
-
-```
-+--------------------------------------------------------------------+
-| STRYX Scan Results                                                 |
-| Target: http://localhost:8000                                      |
-| Total Findings: 3                                                  |
-| Breakdown: CRITICAL: 1 | HIGH: 1 | MEDIUM: 1                     |
-+--------------------------------------------------------------------+
-
-[#] [CRITICAL] Unauthenticated access to /admin
-    Endpoint: http://localhost:8000/admin
-    CWE: CWE-306 | Scanner: auth
-    Confidence: 70%
-    Evidence: GET http://localhost:8000/admin -> 200
-```
-
-## Roadmap
-
-### v0.1 (this build)
-
-- [ ] HTTP crawler
-- [ ] Endpoint discovery
-- [ ] Authentication scanning
-- [ ] Authorization testing
-- [ ] Basic injection testing
-- [ ] JSON/HTML reports
-
-### v0.5
-
-- [ ] Browser automation
-- [ ] GraphQL support
-- [ ] Multi-threaded fuzzing
-- [ ] AI attack planning
-- [ ] Custom payloads
-- [ ] Plugin SDK
-
-### v1.0
-
-- [ ] Autonomous attack chaining
-- [ ] Headless browser exploitation
-- [ ] CI/CD integration
-- [ ] Distributed scanning
-- [ ] Cloud dashboards (MEDUSA integration)
-- [ ] AI-powered exploit reasoning
-
-## Contributing
-
-See [CONTRIBUTING.md](CONTRIBUTING.md) for guidelines.
-
-## Security Policy
-
-See [SECURITY.md](SECURITY.md) for reporting vulnerabilities in STRYX itself.
-
-## License
-
-Apache License 2.0. See [LICENSE](LICENSE).
-
-## Author
-
-Built by Akhilesh Varma (ak495867) under Medusa Security.
+# STRYX
+
+**AI-Powered Dynamic Application Security Testing (DAST)**
+
+[![License](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](LICENSE)
+[![Python Version](https://img.shields.io/badge/python-3.11+-blue.svg)](https://www.python.org/downloads/)
+[![Build Status](https://github.com/medusa-Security/stryx/actions/workflows/ci.yml/badge.svg)](https://github.com/medusa-Security/stryx/actions)
+
+STRYX is a developer-first, AI-assisted DAST engine that crawls, maps, and tests the live attack surface of web applications. It discovers hidden endpoints, simulates real attacker behavior, and detects exploitable vulnerabilities with minimal false positives. Every finding carries full evidence (request, response, status code, payload, confidence score) -- no heuristic-only results.
+
+**Design philosophy: high signal, low noise.**
+
+## How It Fits Into MEDUSA
+
+- **Remy** -- SAST, analyzes source code pre-deployment.
+- **STRYX** -- DAST, validates a running application's live attack surface and exploitability.
+- **MEDUSA** -- Aggregates findings from both, correlates static and runtime issues, estimates business impact, provides centralized security management.
+
+## Architecture
+
+```
+CLI -> Configuration -> Attack Orchestrator -> { Endpoint Discovery }
+                                                        |
+                                         Authentication Engine
+                                         Authorization Engine
+                                         Injection Engine
+                                         API Fuzzer
+                                         AI Attack Planner
+                                         Evidence Collector
+                                         Report Generator
+                                                        |
+                                              Target Application
+```
+
+## Installation
+
+```bash
+# From PyPI
+pip install stryx
+
+# From source
+git clone https://github.com/Medusa-Security/stryx.git
+cd stryx
+pip install -e .
+```
+
+## Quickstart
+
+```bash
+# Run a full scan
+stryx scan http://localhost:8000
+
+# Output:
+# STRYX Scan Results
+# Target: http://localhost:8000
+# Total Findings: 3
+# Breakdown: CRITICAL: 1 | HIGH: 1 | MEDIUM: 1
+```
+
+## Core Modules
+
+| Module | Purpose |
+|--------|---------|
+| Endpoint Discovery | Crawls targets, extracts APIs from OpenAPI/Swagger, sitemaps, JS files, GraphQL |
+| Authentication Scanner | Tests missing auth, weak JWTs, session fixation, cookie security |
+| Authorization Scanner | Tests IDOR, privilege escalation, admin access, multi-tenant escape |
+| Injection Engine | SQL, NoSQL, command, SSRF, path traversal, XXE, SSTI, LDAP injection |
+| API Fuzzer | Parameter mutation, boundary values, type confusion, nested JSON |
+| CORS Scanner | Detects misconfigured CORS policies and origin reflection |
+| GraphQL Scanner | Tests introspection exposure, query depth limiting |
+| AI Attack Planner | Constructs multi-step attack chains across findings |
+| Evidence Engine | Enforces evidence requirements on every finding |
+
+## CLI Reference
+
+### Commands
+
+| Command | Description |
+|---------|-------------|
+| `stryx scan <url>` | Run full security scan |
+| `stryx crawl <url>` | Crawl and discover endpoints |
+| `stryx auth <url>` | Run authentication tests |
+| `stryx fuzz <url>` | Run API fuzzing tests |
+| `stryx report <url>` | Generate reports |
+| `stryx config` | View/update configuration |
+| `stryx providers` | List supported AI providers |
+| `stryx update` | Update STRYX |
+
+### Flags
+
+| Flag | Description |
+|------|-------------|
+| `--deep` | Enable deep scanning |
+| `--json <file>` | Output JSON report |
+| `--html <file>` | Output HTML report |
+| `--markdown <file>` | Output Markdown report |
+| `--threads <n>` | Concurrent threads (1-200) |
+| `--timeout <s>` | HTTP timeout in seconds |
+| `--headers <json>` | Custom headers |
+| `--cookies <str>` | Authentication cookies |
+| `--proxy <url>` | HTTP proxy |
+| `--wordlist <file>` | Custom wordlist |
+| `--rate <n>` | Requests per second limit |
+
+## Configuration
+
+```yaml
+provider: groq
+model: llama-3.3-70b-versatile
+threads: 20
+timeout: 10
+crawl_depth: 5
+respect_robots: false
+ai_attack_planning: true
+modules:
+  auth: true
+  authorization: true
+  injection: true
+  fuzzing: true
+```
+
+Supported AI providers: Groq, OpenAI, Anthropic, OpenRouter, Ollama, XAI, NVIDIA NIM.
+
+## Sample Report
+
+```
++--------------------------------------------------------------------+
+| STRYX Scan Results                                                 |
+| Target: http://localhost:8000                                      |
+| Total Findings: 3                                                  |
+| Breakdown: CRITICAL: 1 | HIGH: 1 | MEDIUM: 1                     |
++--------------------------------------------------------------------+
+
+[#] [CRITICAL] Unauthenticated access to /admin
+    Endpoint: http://localhost:8000/admin
+    CWE: CWE-306 | Scanner: auth
+    Confidence: 70%
+    Evidence: GET http://localhost:8000/admin -> 200
+```
+
+## Roadmap
+
+### v0.1 (this build)
+
+- [ ] HTTP crawler
+- [ ] Endpoint discovery
+- [ ] Authentication scanning
+- [ ] Authorization testing
+- [ ] Basic injection testing
+- [ ] JSON/HTML reports
+
+### v0.5
+
+- [ ] Browser automation
+- [ ] GraphQL support
+- [ ] Multi-threaded fuzzing
+- [ ] AI attack planning
+- [ ] Custom payloads
+- [ ] Plugin SDK
+
+### v1.0
+
+- [ ] Autonomous attack chaining
+- [ ] Headless browser exploitation
+- [ ] CI/CD integration
+- [ ] Distributed scanning
+- [ ] Cloud dashboards (MEDUSA integration)
+- [ ] AI-powered exploit reasoning
+
+## Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for guidelines.
+
+## Security Policy
+
+See [SECURITY.md](SECURITY.md) for reporting vulnerabilities in STRYX itself.
+
+## License
+
+Apache License 2.0. See [LICENSE](LICENSE).
+
+## Author
+
+Built by Akhilesh Varma (ak495867) under Medusa Security.

{stryx_cli-0.1.0 → stryx_cli-0.1.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "stryx-cli"
-version = "0.1.0"
+version = "0.1.2"
 description = "AI-Powered Dynamic Application Security Testing (DAST) -- part of the MEDUSA security platform"
 readme = "README.md"
 license = {text = "Apache-2.0"}

{stryx_cli-0.1.0 → stryx_cli-0.1.2}/stryx/ai/attack_planner.py

@@ -82,16 +82,14 @@ class AttackPlanner:
 
         return chains
 
-    async def _generate_remediation(
-        self, findings: list[Finding], provider: AIProvider
-    ) -> None:
+    async def _generate_remediation(self, findings: list[Finding], provider: AIProvider) -> None:
         """Generate AI-powered remediation for each finding."""
         logger.info(f"Generating remediation for {len(findings)} findings")
 
         # Process findings in batches to avoid token limits
         batch_size = 10
         for i in range(0, len(findings), batch_size):
-            batch = findings[i:i + batch_size]
+            batch = findings[i : i + batch_size]
 
             for finding in batch:
                 if finding.remediation:
@@ -128,9 +126,7 @@ class AttackPlanner:
                     logger.debug(f"Failed to generate remediation for {finding.title}: {e}")
                     continue
 
-    async def _ai_plan_chains(
-        self, findings: list[Finding], provider: AIProvider
-    ) -> list[AttackChain]:
+    async def _ai_plan_chains(self, findings: list[Finding], provider: AIProvider) -> list[AttackChain]:
         """Use AI to generate attack chains."""
         findings_data = [f.to_dict() for f in findings]
         findings_text = format_findings_for_prompt(findings_data)
@@ -168,9 +164,7 @@ class AttackPlanner:
                 for step_data in chain_data.get("steps", []):
                     if isinstance(step_data, dict):
                         # Find matching finding
-                        matching_finding = self._find_matching_finding(
-                            findings, step_data.get("title", "")
-                        )
+                        matching_finding = self._find_matching_finding(findings, step_data.get("title", ""))
                         if matching_finding:
                             chain.add_step(
                                 matching_finding,
@@ -187,9 +181,7 @@ class AttackPlanner:
             logger.warning(f"Failed to parse AI response: {e}")
             return []
 
-    def _find_matching_finding(
-        self, findings: list[Finding], title: str
-    ) -> Finding | None:
+    def _find_matching_finding(self, findings: list[Finding], title: str) -> Finding | None:
         """Find a finding matching the given title."""
         title_lower = title.lower()
         for f in findings: