Skip to content

JGD v2.1.1 — Standalone binaries (exe / Linux) + packaging fixes

Latest

Choose a tag to compare

@lupingQAQ lupingQAQ released this 08 Oct 10:32

Standalone binaries

No Python installation required — single-file executables (PyInstaller + UPX) with the full agent pipeline inside:

Asset Platform Size SHA-256
jgd-v2.1.1-windows-x64.exe Windows x64 8.6 MB 35aefa9a0ac46173ef729a70cd85aad93ea8876aaeffca09a95726198d7f3b85
jgd-v2.1.1-linux-x64 Linux x64 7.5 MB 7265a0dff171afedc721c70c4741ca8e96bb18d76513344d91346a6bf94ebd76

Quick start:

# audit any JAR directory  (report -> audit_report/, state -> data/, PoCs -> pocs/)
./jgd --target /path/to/jars --name "your-product"

# interactive chain-tree TUI
./jgd --tui

Notes:

  • First run provisions config/ and examples/ next to the binary; all artifacts are written next to it. Set JGD_ROOT to relocate the workspace.
  • Runtime requirements unchanged: JDK 11 & 17 on PATH for dynamic probes and PoC firing; LLM credentials via config/models.json (template: config/models.example.json) or JGD_* environment variables.
  • chromadb is optional and not bundled — RAG persistence degrades to a no-op store; the mining / verification / PoC pipeline runs normally without it.
  • Windows: use Windows Terminal for full TUI colors. SmartScreen may warn on unsigned binaries.

Changes

  • jgd/__main__ unified entry: audit CLI, --tui, and -m <module> stage dispatch — the multi-stage pipeline (stages spawned through sys.executable) keeps working inside a frozen binary
  • Portable PROJECT_ROOT: executable directory when frozen, JGD_ROOT env override
  • chromadb is now genuinely optional (VStore no-op fallback instead of ImportError)
  • Console-encoding robustness: UTF-8 output regardless of host codepage; stage output decoded as UTF-8
  • Fix: TUI crash in English mode (negative format width on the 65-char subtitle)
  • Fix: TUI crash on non-tty stdin under POSIX (termios.error is not an OSError subclass)
  • Fix: pocs/ directory creation on fresh workspaces