# denoyey/burpsuitepro architecture

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

- Interactive diagram: https://gitdiagram.com/denoyey/burpsuitepro
- Repository: https://github.com/denoyey/burpsuitepro

## Overview

##### Project type and purpose
- This is neither a typical full-stack app nor a compiler: it’s an installer/packaging project for “Burp Suite Professional v2025.”
- Its purpose is to automate downloading, installing, configuring, updating, and launching Burp Suite Pro on Linux and Windows, including license-loader integration.

##### File structure
- Top-level files:
- README.md – user guidance
- install.sh – Linux installer script
- install.ps1 – Windows PowerShell installer script
- update.sh – optional Linux updater
- loader.jar – license-loader component
- No “src” or “lib” directory: the project is a thin wrapper around existing binaries/jars.
- Key interactions: scripts invoke Java, download resources from GitHub, place files in OS locations, create desktop/menu entries.

##### README for additional insights
- Describes two flows: Linux and Windows installation.
- Shows manual steps for licensing (copying request/response keys between Burp and loader).
- Mentions external dependencies: Java runtime and GitHub repository for scripts and assets.

##### Main components
a. User Environment
- Linux shell (bash)
- Windows PowerShell
b. Installer Scripts
- install.sh / update.sh (Linux)
- install.ps1 (Windows)
c. External Repository (GitHub)
d. Java Runtime
- update-alternatives management on Linux
- System‐default Java on Windows
e. Burp Suite Pro Application
- loader.jar (license bypass tool)
- burpsuitepro JAR or executable
f. OS Integration
- Desktop launcher (xfce .desktop file)
- Windows Start Menu shortcut & .vbs wrapper
g. Manual Activation Step
- Burp request key ↔ loader.jar request/response

##### Relationships and interactions
- User runs installer script → script fetches assets from GitHub → places loader.jar + burp files in installation directory
- Script configures Java (Linux: update-alternatives; Windows: expects preconfigured Java)
- Script creates desktop/menu entries pointing to a launcher that runs:
Java –jar loader.jar –load burp request/response → launches Burp Suite
- update.sh repeats download/update steps

##### Architectural patterns & design principles
- “Separation of Concerns”: installer logic is in scripts, licensing logic in loader.jar, application logic in Burp Suite itself
- “Externalization of Configuration”: scripts reference URLs and OS paths
- “Idempotent Deployment”: update.sh can be rerun to pull latest versions

- User (actor)
- Installer script
- Java runtime
- loader.jar & burpsuitepro components
- OS integration targets
- Manual activation loop between burpsuitepro and loader.jar
- Optional steps (e.g., update.sh on Linux)

## Diagram (Mermaid)

```mermaid
flowchart TB
    %% Swimlanes
    subgraph "Linux Flow"
        direction TB
        UL["User (bash)"]:::user
        LS["install.sh"]:::script
        US["update.sh"]:::script
        JL["Java Runtime"]:::runtime
        LO["loader.jar"]:::component
        BP_L["Burp Suite Pro"]:::app
        DE["Desktop Entry (.desktop)"]:::os
        MA_L["Manual Activation"]:::manual
    end

    subgraph "Windows Flow"
        direction TB
        UW["User (PowerShell)"]:::user
        PS["install.ps1"]:::script
        JW["Java Runtime"]:::runtime
        LO2["loader.jar"]:::component
        BP_W["Burp Suite Pro"]:::app
        SM["Start Menu Shortcut & .vbs"]:::os
        MA_W["Manual Activation"]:::manual
    end

    %% External Service
    GH["GitHub Repository"]:::external

    %% Edges - Linux
    GH -->|HTTP GET assets| LS
    GH -->|HTTP GET updates| US
    UL -->|runs| LS
    UL -->|runs| US
    LS -->|invokes| JL
    LS -->|deploys| LO
    LS -->|deploys| BP_L
    LS -->|creates| DE
    US -->|fetch updates| JL
    US -->|updates assets| LO
    US -->|updates| BP_L
    JL -->|java -jar| LO
    LO -->|load license| BP_L
    BP_L -->|request key| MA_L
    MA_L -->|response key| BP_L

    %% Edges - Windows
    GH -->|HTTP GET assets| PS
    UW -->|runs| PS
    PS -->|invokes| JW
    PS -->|deploys| LO2
    PS -->|deploys| BP_W
    PS -->|creates| SM
    JW -->|java -jar| LO2
    LO2 -->|load license| BP_W
    BP_W -->|request key| MA_W
    MA_W -->|response key| BP_W

    %% Click Events
    click README.md "https://github.com/denoyey/burpsuitepro/blob/main/README.md"
    click LS "https://github.com/denoyey/burpsuitepro/blob/main/install.sh"
    click US "https://github.com/denoyey/burpsuitepro/blob/main/update.sh"
    click PS "https://github.com/denoyey/burpsuitepro/blob/main/install.ps1"
    click LO "https://github.com/denoyey/burpsuitepro/blob/main/loader.jar"
    click LO2 "https://github.com/denoyey/burpsuitepro/blob/main/loader.jar"

    %% Styles
    classDef script fill:#D0E7FF,stroke:#0366d6;
    classDef external fill:#DFF2BF,stroke:#4F8A10;
    classDef runtime fill:#FFE7B3,stroke:#D78F00;
    classDef os fill:#F0F0F0,stroke:#888888;
    classDef component fill:#FFE2E2,stroke:#D8000C;
    classDef app fill:#E8E2FF,stroke:#5B2F90;
    classDef user fill:#FFFFFF,stroke:#000000,stroke-dasharray: 2 2;
    classDef manual fill:#FFF4E5,stroke:#FFA500,stroke-dasharray: 3 3;
```
