How jumbo-wjb/jpentest works
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.