Skip to content

Releases

v1.18.1

Choose a tag to compare

@github-actions github-actions released this 15 Nov 20:31
  • Reinstalling after deleting the kit works. A kit.json pointer left by a
    deleted kit folder, or naming this checkout after its sandbox was removed,
    stopped every later install with "Invalid owner pointer" and nothing could
    repair it. The installer now installs here, backs the old pointer up and
    registers this checkout. A pointer to another existing folder with a broken
    receipt still fails. maintain.cmd -Apply in a checkout with no installed
    manifest no longer fails.
  • re-triage --timeout really stops a hung analyzer. Killing cmd.exe left the
    tool behind a .cmd shim running with the output pipes open, so triage waited
    for it anyway; a 1-second timeout waited 19 seconds in the reproducer. The
    whole process tree is now ended.
  • FLOSS, UnityPy and Capstone update again. The 1.4.0 update list was never
    extended when they were added, so they stayed at their first installed
    version. Every catalog package without a pin now follows its registry; capa
    stays locked to its release tag.
  • Downloads give up on a stalled connection (30 s connect timeout, 2-minute
    stall limit, retried) instead of hanging the install.
  • New uninstall section in docs/standalone.md.

v1.18.0

Choose a tag to compare

@github-actions github-actions released this 15 Nov 16:34
  • New optional tool fmodel-mcp (FModel MCP 1.2.0): a stdio MCP server on
    CUE4Parse that lets an agent open, search, inspect and export Unreal
    .pak/IoStore archives without the FModel GUI. Installed from the
    self-contained release zip after its GitHub SHA-256 check; the kit does not
    run its installer or register it with a client. Route, config and key
    handling in docs/unreal-mcp.md, which also points to UEFormat for bringing
    exports into Blender or Unreal.
  • reverse-api-engineer 0.15.0 -> 0.16.0, with the upstream agent skill from
    the same tag. 0.16.0 adds an engineer-only hermes backend (your own Hermes
    model and sign-in) and an optional codex extra, removes collector mode and
    fixes --model for non-Claude SDKs and slow pages in chrome-mcp runs.
  • Currency sweep of all 95 catalog tools: every other tool is at its upstream
    latest release. Supplied snapshots reviewed and their owners recorded in
    docs/companions.md; Marvel Rivals-specific tools are left to a Rivals forge.

v1.17.2

Choose a tag to compare

@github-actions github-actions released this 14 Nov 08:11
  • Fix Update-ReverseThis.ps1 with no arguments under Windows PowerShell 5.1:
    $PSScriptRoot is empty in an advanced script's param() defaults, so the
    updater had no destination and stopped with "The path is not of a legal
    form". The default is now set in the script body.
  • The updater hands a digest-verified release to that release's own updater
    (once, guarded). A 1.16.1 ZIP install could not reach 1.17 because its
    updater rejected the new skills/ folder; future layout changes are judged
    by the release that introduces them.
  • Installs from 1.17.1 or older: run the latest release's updater once with
    -Destination <kit> (documented in docs/standalone.md). Found by updating a
    real 1.16.1 ZIP install; its private work files were preserved.

v1.17.1

Choose a tag to compare

@github-actions github-actions released this 14 Nov 08:03
  • re-triage uses the kit it is installed in. It read the shared owner pointer
    first, so a second or -InstallRoot kit listed the owner's analyzers (tools it
    did not have) and wrote its workspace into the owner's sandbox/work. Order is
    now: --kit, the script's own kit, then the owner pointer for a source checkout
    without a sandbox.
  • -Doctor without -Only verifies every installed tool and lists unselected
    catalog tools as optional instead of failing, so a kit built with -Only passes.
    A tool named with -Only must still be installed, and a kit with nothing
    installed still fails.
  • Found by installing the published 1.17.0 ZIP into a fresh folder (spaces, !,
    parentheses) with one tool per install method: all eight installed with
    verified digests and every shim ran.

v1.17.0

Choose a tag to compare

@github-actions github-actions released this 14 Nov 01:01
  • Update reverse-api-engineer to 0.15.0 (MIT, PyPI). Checked in an isolated
    venv and then in the kit: --version, list --json, and agent --dry-run
    with --headless and with the auto provider all pass. 0.15.0 keeps Claude
    runs away from the user's Claude Code settings, hooks and MCP servers, and
    reports status: error when no client was written.
  • Ship the upstream agent skill for the same tag in
    skills/reverse-api-engineer/ (unmodified, with its MIT licence and an
    UPSTREAM.md naming the commit and the kit-specific differences). Release
    ZIPs include skills/, and the source updater accepts it.
  • docs/web-api.md covers the new chrome-mcp default (no HAR; use
    --headless or agent_provider: auto for a reusable capture) and why the
    shim is called from PowerShell rather than Git Bash.

v1.16.1

Choose a tag to compare

@github-actions github-actions released this 13 Nov 19:57
  • Update REA to 6.9.0 (exact npm pin and integrity). Installed in an isolated
    root first, then rea doctor --provider ghidra, a read-only analysis of
    notepad.exe (853 procedures) and rea mcp doctor (255 tools, 6 prompts)
    passed with both the isolated Ghidra 12.1.4 and the kit default Ghidra 12.2.
    6.9.0 admits any Ghidra 12.x from 12.1; the shim still prefers the verified
    12.1.4 copy and keeps a caller's own GHIDRA_INSTALL_DIR.
  • Follow Detect It Easy 4.0.0: its Windows asset is now die_win64_qt6_<version>.zip,
    so the old portable pattern silently held the kit on 3.21. The Qt6 build was
    checked against 3.21 on the same PE and .NET files before switching.
  • scripts/check_upstreams.py follows the 6.9.0 range: Ghidra 12.1 and 12.2
    report compatible, 12.0 incompatible, any other REA version
    unknown-version until it is reviewed.
  • The companion check reads the bundle's PACKS.json reverse pack (enable
    command, owner, floor, ReverseThis/kit.json detection) instead of README
    prose; the bundle 8.41 README rewrite had made the old check report false drift.
  • Refresh the companion snapshot table: each supplied snapshot is compared with
    its upstream and given an owner (OBS MCP, both Unity MCPs, game-dev skills and
    Blender belong to the Starter Bundle; none is catalogued here).

v1.16.0

Choose a tag to compare

@github-actions github-actions released this 13 Nov 00:22
  • Add re-triage: the first command for a target you have not seen. Give it a
    file or a game folder and it answers in one JSON document: what the target is
    and the evidence for that, every analyzer in the kit that reads it and whether
    it is installed, and the commands to run next.
  • Formats are read from the bytes, not the extension: native, .NET, Go, UPX and
    PyInstaller PE files, ELF, Mach-O, WebAssembly, Java classes, DEX, APK, JAR,
    asar, common archives, Unity bundles and IL2CPP metadata, Unreal pak, IoStore
    and packages, Godot packs, GameMaker data, Valve VPK and BSP, REDengine
    archives, DDS, Switch containers, Lua and Python bytecode.
  • A folder is identified by engine (Unity Mono or IL2CPP, Unreal, Godot,
    GameMaker, Source, Electron, Ren'Py, RPG Maker, REDengine, Creation Engine,
    Java) and the report points at the files that matter: for an IL2CPP game, the
    GameAssembly.dll and global-metadata.dat pair the dumper needs.
  • re-triage --run executes only the quick, read-only static analyzers that are
    installed (pe-recon, diec, rz-bin, 7z l, texdiag) with a time limit
    each, and keeps their output with the report under
    sandbox/work/<name>-<hash>/triage. A missing or failing tool is listed and
    the rest still run. The target is never executed, loaded or modified.
  • Slow or interactive tools (capa, FLOSS, Ghidra, debuggers) are offered as next
    commands, not run for you.
  • An unrecognised file says so, with its first bytes, instead of guessing.

v1.15.2

Choose a tag to compare

@github-actions github-actions released this 12 Nov 21:07
  • Unattended runs no longer stall or abort on an unanswered UAC prompt. A failed
    Node or Python patch upgrade keeps the working runtime with a warning; it is
    fatal only when no compatible runtime remains.
  • A failed JDK install is attempted once per run. Later Java tools fail at once
    with the first reason instead of each waiting for another prompt.
  • Each run writes sandbox/last-run.json (ok and failed tool ids) so a
    caller can report a partial run without parsing the log. Failed tools keep any
    previously installed version.
  • A kit folder move no longer leaves silent broken Python tools: pip console
    launchers keep the old absolute path. Doctor now reports such a venv, and a
    normal install rebuilds it with venv --clear.

v1.15.1

Choose a tag to compare

@github-actions github-actions released this 08 Nov 18:46
  • The REA shim now prefers the isolated sandbox/tools/ghidra-12.1.4 copy that
    REA 6.8.0 supports, while still honoring a caller-supplied
    GHIDRA_INSTALL_DIR. It discovers a JDK 21+ when the REA entry does not
    declare one, and runs the npm shim in a child cmd so REA's endlocal does
    not discard the selected paths or leak PATH/JAVA_HOME to the caller.
  • Added installer regressions for isolated-Ghidra preference, caller override,
    and repeated shim generation.
  • Website API documentation now names the actual provider requirements and
    keeps catalog/tools.json as the single version source.

v1.15.0

Choose a tag to compare

@github-actions github-actions released this 08 Nov 18:07
  • Added optional reverse-api-engineer 0.14.0 (MIT, published PyPI release) as
    a private pip-venv catalog tool with a stable reverse-api-engineer shim.
    It does not register MCP, start a browser, install a global Python package or
    alter REA/REA MCP settings.
  • Added docs/web-api.md, task routing in AGENTS.md and docs/coverage.md,
    and contract tests. The integration keeps generated clients and HAR captures
    under ignored sandbox/work/web-api; the stable release is pinned instead of
    mixing in unreleased main skill changes.