# jumbo-wjb/jpentest architecture

> Architecture diagram of the GitHub repository jumbo-wjb/jpentest, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2025-10-26). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/jumbo-wjb/jpentest
- Repository: https://github.com/jumbo-wjb/jpentest

## Overview

##### Project type and purpose
- JPentest is a command-line penetration-testing toolkit written in Python. It is not a multi-tier web app but a modular CLI utility that performs various web-recon and brute-force tasks (domain enumeration, directory brute forcing, AppScan report fetching, login brute forcing, subdomain brute forcing).

##### File structure
- Top-level:
- JPentest.py – the single CLI entry point
- README.md – usage instructions and example outputs
- dict/ – wordlists used by the brute-force modules
- modules/ – one file per test module (appscan.py, brute_pass.py, dir.py, domain.py, subdomain_brute.py)
- pic/ – sample screenshots
- No frontend/backend folder separation, but a clear “plugin” pattern under modules/, and external resource files under dict/.

##### README for additional insights
- The tool uses standard CLI flags (-m to pick a module, ‑u or ‑a for target, ‑d for dict, etc.).
- It outputs results to a save_path if provided.
- It likely relies on Python HTTP libraries (e.g., requests) and threading.

a. Main components
- CLI Entrypoint (JPentest.py) – parses flags and invokes the Module Manager
- Module Manager – selects and loads the requested module from modules/
- Modules (Domain, Dir, Appscan, Brute_pass, Subdomain_brute) – implement specific scanning logic
- Dictionary Resources (dict/*.txt) – wordlists fed into brute-force modules
- Networking Layer – HTTP client library used by modules to issue requests
- Output Handler – writes results to stdout or to the specified save_path
- External Targets – the web servers or AppScan service being tested

b. Relationships and interactions
- User → CLI Entrypoint: issues a command
- CLI Entrypoint → Module Manager: passes parsed arguments
- Module Manager → Chosen Module: calls module.run(target, options)
- Module → Networking Layer: makes HTTP requests
- Brute-force modules → Dictionary Resources: read wordlists and iterate
- Module → Output Handler: formats and saves/displays results

c. Architectural patterns and principles
- Plugin/Modular architecture: each test type is its own module file
- Single responsibility: JPentest.py handles CLI, modules handle logic
- Resource abstraction: common dict folder for data inputs
- Threading support: modules can spin off threads (-t flag) for concurrency

d. Key technologies
- Python 3.x
- Standard library for CLI parsing (argparse)
- requests or urllib3 for HTTP
- threading or concurrent.futures for parallelism
- Plain-text wordlist files under dict/

##### Final recommendations
- Modules visually under a “modules/” folder boundary to show they are peers.
- Don’t over-segment; focus on the six major elements above. This will capture all essential architecture without unnecessary detail.

## Diagram (Mermaid)

```mermaid
flowchart TD
    User["User"]:::external
    CLI["CLI Entrypoint"]:::control
    Manager["Module Manager"]:::control

    subgraph "Modules Directory"
        direction TB
        Domain["Domain Enumeration Module"]:::plugin
        Dir["Directory Brute-forcing Module"]:::plugin
        AppScan["AppScan Report Fetch Module"]:::plugin
        BrutePass["Login Brute-force Module"]:::plugin
        Subdomain["Subdomain Brute-force Module"]:::plugin
    end

    Dictionary["Dictionary Store"]:::resource
    Net["Networking Layer"]:::io
    Output["Output Handler"]:::io
    External["External Target (Web Server/AppScan)"]:::external

    User -->|"issues command"| CLI
    CLI -->|"parse flags"| Manager
    Manager -->|"load module"| Domain
    Manager -->|"load module"| Dir
    Manager -->|"load module"| AppScan
    Manager -->|"load module"| BrutePass
    Manager -->|"load module"| Subdomain

    Domain -->|"HTTP requests"| Net
    Dir -->|"HTTP requests"| Net
    AppScan -->|"HTTP requests"| Net
    BrutePass -->|"HTTP requests"| Net
    Subdomain -->|"HTTP requests"| Net

    Dir -->|"read wordlist"| Dictionary
    BrutePass -->|"read wordlist"| Dictionary
    Subdomain -->|"read wordlist"| Dictionary

    Net -->|"network I/O"| External

    Domain -->|"format results"| Output
    Dir -->|"format results"| Output
    AppScan -->|"format results"| Output
    BrutePass -->|"format results"| Output
    Subdomain -->|"format results"| Output

    click CLI "https://github.com/jumbo-wjb/jpentest/blob/master/JPentest.py"
    click Manager "https://github.com/jumbo-wjb/jpentest/blob/master/JPentest.py"
    click Domain "https://github.com/jumbo-wjb/jpentest/blob/master/modules/domain.py"
    click Dir "https://github.com/jumbo-wjb/jpentest/blob/master/modules/dir.py"
    click AppScan "https://github.com/jumbo-wjb/jpentest/blob/master/modules/appscan.py"
    click BrutePass "https://github.com/jumbo-wjb/jpentest/blob/master/modules/brute_pass.py"
    click Subdomain "https://github.com/jumbo-wjb/jpentest/blob/master/modules/subdomain_brute.py"
    click Dictionary "https://github.com/jumbo-wjb/jpentest/tree/master/dict/"
    click Output "https://github.com/jumbo-wjb/jpentest/blob/master/JPentest.py"

    classDef control fill:#AEDFF7,stroke:#036,stroke-width:1px
    classDef plugin fill:#D5F5E3,stroke:#063,stroke-width:1px
    classDef resource fill:#FCF3CF,stroke:#D4AC0D,stroke-width:1px
    classDef io fill:#FADBD8,stroke:#C0392B,stroke-width:1px
    classDef external fill:#E8DAEF,stroke:#7D3C98,stroke-width:1px
```
