Files
reverse-engineering-anything/THIRD_PARTY_NOTICES.md
T
5c59bdc8a6 feat(ghidra)!: verify the bridge on Ghidra 12.2 (#12081)
* feat(ghidra)!: verify the bridge on Ghidra 12.2

Admit 12.x from minor 2 upward, with 12.2 and JDK 25 as the verified
pair. The bridge now calls the four-argument storage API added in 12.2,
so 12.1.x cannot compile it and is no longer accepted.

BREAKING CHANGE: Ghidra 12.1.x is rejected. Use Ghidra 12.2 or another
12.x build at or above minor 2, and a JDK inside that installation's
declared range (25 or newer for the verified 12.2 build).

* docs(ghidra): point remaining lanes at Ghidra 12.2

The Windows, 6502, and m68k prerequisites still named 12.1.4 and JDK 21,
which the verified-build check now rejects. The bridge compile lane names
the 12.2 jars it actually compiles against.

Co-authored-by: morluto <morluto@users.noreply.github.com>

* test(ghidra): admit the JDK the verified install declares

The Java home framing probe still reported JDK 21 while the verified
installation fixture now declares a minimum of 25, so doctor admission
failed before the path framing was checked.

Co-authored-by: morluto <morluto@users.noreply.github.com>

* test(ghidra): derive admitted install fixtures from the verified release

Boundary hosts and assertions still named Ghidra 12.1.4 after admission
moved to 12.2, so list_procedures evidence and completed property reads
disagreed with the install the provider actually reported.

Co-authored-by: morluto <morluto@users.noreply.github.com>

* fix(ghidra): record the exact 12.2 Clang switch-recovery defect

Ghidra 12.2 stays the verified build. Sessions and decompiler results on
that exact version name upstream issue 9996 and the 12.2.1 fix commit.
Other version strings, including 12.2.1, do not carry the limitation.

Co-authored-by: morluto <morluto@users.noreply.github.com>

* test(ghidra): check switch-defect facts instead of the warning sentence

The policy test keeps the structured defect record and checks that the
owning formatter delivers its id, commit, release, and scope fields.

Co-authored-by: morluto <morluto@users.noreply.github.com>

* test(browser): name the Playwright launch boundary the lifecycle catalog checks

Main retitled that case with a platform placeholder. The coverage catalog
still required the old literal, so the merged full suite reported a missing
title.

Co-authored-by: morluto <morluto@users.noreply.github.com>

* test(browser): point the lifecycle catalog at main's launch title

The merged suite uses main's platform-specific Playwright launch test.
The coverage catalog now names that title, and this branch keeps main's
test body so the merge stays clean.

Co-authored-by: morluto <morluto@users.noreply.github.com>

* test(browser): cover the platform launch title on this branch

The lifecycle catalog names main's platform launch title. This branch
now has that quoted test too, so the check passes before and after the
merge.

Co-authored-by: morluto <morluto@users.noreply.github.com>

* fix(ghidra): record the exact 12.2 masked byte-switch defect

Ghidra 12.2 leaves an AArch64 and-0xff byte-offset switch unrecovered.
Exact 12.2 sessions now cite open upstream issue 10154, and the AArch64
lane expects that jump table to stay unrecovered.

Co-authored-by: morluto <morluto@users.noreply.github.com>

* test(browser): keep one platform launch environment check

The second launch test repeated the selected environment check. The
remaining test is the parameterized title, and the launcher forwards
SYSTEMROOT on win32 so that assertion holds.

Co-authored-by: morluto <morluto@users.noreply.github.com>

* fix(ghidra): keep the open switch defect on admitted builds

The exact-version check cleared ghidra-10154 on every build except 12.2.
That defect stays on admitted releases until one is known to fix it.
ghidra-9996 still clears after the exact 12.2 build.

Co-authored-by: morluto <morluto@users.noreply.github.com>

* style(docs): format the Ghidra testing-lane table

The AArch64 jump-table row wrapped past the formatter width and failed
static checks.

Co-authored-by: morluto <morluto@users.noreply.github.com>

* test(ghidra): give the masked switch its full byte range

The unrecovered oracle now uses 256 readable table bytes, and the same
object must still recover its compare-bounded switch.

Co-authored-by: morluto <morluto@users.noreply.github.com>

* docs(website): point Ghidra setup at 12.2 and JDK 25

The public setup pages still told new users to install Ghidra 12.1.4 and
JDK 21, which this release rejects. Changed setup sentences are extracted
and left untranslated so those editions use the English page.

Co-authored-by: morluto <morluto@users.noreply.github.com>

* docs(website): keep catalog edits to the changed setup strings

The catalog check compares active message ids, not a full rewrite.
Restore the previous catalogs and update only the Ghidra 12.2 setup
strings, leaving their translations empty.

Co-authored-by: morluto <morluto@users.noreply.github.com>

* fix(ghidra): apply the closed switch defect from the parsed patch

12.2, 12.2.0, and 12.2.0 with a suffix all precede 12.2.1, so they keep
ghidra-9996. The masked-switch table lists all 256 byte entries.

Co-authored-by: morluto <morluto@users.noreply.github.com>

* fix(ghidra): share the AArch64 switch fixture compiler invocation

---------

Co-authored-by: Cursor Agent <cursoragent@cursor.com>
Co-authored-by: morluto <morluto@users.noreply.github.com>
2026-11-18 16:06:51 -05:00

27 KiB
Raw Blame History

Third-party notices

REA-authored code is licensed under MIT. Third-party material retains its own copyright, license, attribution, and NOTICE requirements. REA's MIT license grants no rights to proprietary analysis tools. Project and product names identify integrations; they do not imply affiliation or endorsement.

This inventory covers the locked npm dependency graph, code or assets derived from upstream projects, and separately obtained engines used by REA. A listed integration is not a statement that its executable is bundled. Upstream components and caller-selected versions may have additional terms; retain the notices supplied with the software you actually obtain or redistribute.

Distributed dependencies, derived code, and assets

Material Use and licensing records
npm dependencies Complete inventory of every entry in package-lock.json, including transitive, optional platform, development, and website dependencies. Runtime notices preserve the copyright, license, and NOTICE documents from integrity-verified release archives, plus the MIT notice for Rolldown's generated runtime helpers. Development dependencies are inventoried but are not all distributed in REA's npm package.
pefile ordinal tables Import-hash ordinal names are derived from pefile 2024.8.26, copyright 2004–2024 Ero Carrera. Preserve the MIT license. The Python package is not a runtime dependency.
UF2 family names UF2 family IDs and short names are copied from microsoft/uf2 utils/uf2families.json, copyright Microsoft Corporation. Preserve the MIT license.
NativeAOT parser REA's derived parser uses the MIT-licensed ghidra-nativeaot work of Washi and the NativeAOT layout definitions in dotnet/runtime. Preserve Washi's MIT notice and the .NET Foundation MIT notice.
EVM analysis evmole@0.9.3, MIT, copyright 2023 Maxim Andreev. The published npm archive omits its license document; REA retains the original upstream license and provenance. It is also included in the runtime notices.
Windows native addon The release addon is compiled with MinGW-w64 and statically links GCC runtime libraries. Preserve the MinGW-w64 runtime notices, GPLv3 text, and GCC Runtime Library Exception 3.1. The exception governs eligible compiled combinations; it does not relicense the runtime itself under MIT. The Node-API build headers are from Node 22.19.0; its original license and component notices are retained. Node itself is supplied by the user. Snapshot provenance and release-toolchain review requirements are in licenses/README.md.
Dinosaur website example Selected excerpts from wayou/t-rex-runner, derived from Chromium's dinosaur game. The website retains the original BSD-3-Clause notices, including Chromium authors and wayou. This asset is not part of the npm runtime.

Two locked runtime releases, clean-git-ref@2.0.1 (declared Apache-2.0) and minimisted@2.0.1 (declared MIT), omit a full license/copyright document in their published archives and inspected upstream release sources. Their runtime notice entries preserve the declared license and author metadata and include a clearly labeled standard license text. These are documented upstream notice gaps, not recovered copyright notices or a claim that attribution has been fully verified.

The optional frida@17.23.2 npm archive and tagged Node binding source also omit a standalone license/copyright document. Its declared LGPL-2.0 WITH WxWindows-exception-3.1 license is recorded with unchanged Frida licensing text and the GNU Library GPL v2. These are licensing supplements, not recovered Node binding or prebuild-component copyright notices.

Open-source engine credits and licenses

We thank the maintainers and contributors of the projects below. Their decompilers, binary-analysis engines, debuggers, parsers, and capture tools provide capabilities used through REA's integrations. Each row identifies the upstream project, its own license, and its role in REA. In particular, JADX provides the Android decompiler, while jadx-headless-mcp provides the separate headless integration used by REA; both projects deserve credit.

These acknowledgments are voluntary thanks. Required upstream copyright and NOTICE texts remain in their original form and are not replaced by this summary. Credits do not imply endorsement or change any license.

REA's adapters do not grant, replace, or waive these licenses. The upstream executables and their dependency graphs are supplied separately. Git submodules pin inspection sources; they are not included in the npm package.

Project License and source REA relationship
Ghidra Apache-2.0, with the government-work and component qualifications in its NOTICE Bring your own Ghidra; see supported versions. Copies of the 12.2 LICENSE, NOTICE, and DISCLAIMER are retained for reference.
ghidra-nativeaot MIT Pinned inspection source; derived parser attribution above.
JADX Apache-2.0 The audited jadx-headless-mcp source uses JADX 1.5.6 for Android decompilation; the engine JAR is separately supplied.
jadx-headless-mcp Apache-2.0 v0.7.1; pinned submodule and user-supplied JAR.
Kuna Apache-2.0, with its NOTICE Bring your own kuna; REA verified 1.990 and never downloads, installs or bundles it. REA invokes it as a separate process.
Apktool Apache-2.0 User-supplied Android resource decoder.
Binwalk MIT v3.1.0; pinned submodule and user-supplied firmware engine.
Unblob MIT 26.6.4; pinned submodule and user-supplied firmware engine.
Wakaru Apache-2.0 v1.14.0; pinned source and separately obtained JavaScript reconstruction tooling.
WABT Apache-2.0 v1.0.42; external WebAssembly tools; integration provenance.
pwntools MIT, with GPL/BSD component qualifications 4.15.0; caller-supplied offline ELF analysis package.
pyelftools Public-domain dedication and component notices 0.33; includes separately licensed bundled material, including Construct.
Unicorn GPL-2.0 and component notices 2.1.2; used by the caller-supplied ELF analysis profile for instruction emulation.
pwndbg MIT 2026.09.15, commit 55596aa676a2756efb8d67034f31675170eabe48; separately obtained debugger extension.
GNU GDB GPL-3.0-or-later Caller-supplied debugger for the optional pwndbg core-file workflow.
LLDB / LLVM Apache-2.0 with LLVM exceptions Caller-supplied debugger; the installed distribution's component and historical notices also apply.
mitmproxy MIT 12.2.3; separately supplied network capture proxy.
Android Debug Bridge (adb) Apache-2.0 User-supplied Android device tool. A complete Android SDK download has its own SDK license terms; adb's source license does not replace them.
ILSpy / ICSharpCode.Decompiler MIT Optional separately installed .NET decompiler; not a redistributed REA dependency.

Ghidra's original notice credits software developed at the National Security Agency. It explains that US-government-created portions are not subject to US copyright protection, while other portions retain their authors' rights. Its modules include additional third-party licenses, and standalone programs under GPL/ have GPLv3 terms. The three retained top-level documents do not replace the module notices and license directories in a complete Ghidra distribution. REA is not affiliated with or endorsed by the NSA.

Commercial tools and bridges

You must legally obtain the tools and the rights needed for your use. REA does not include an IDA Pro, Hex-Rays decompiler, Hopper, or JEB license, license key, or activation entitlement. A permitted trial/demo may be used only within its official terms. Cracked copies, stolen keys, unauthorized sharing, and bypassing activation or license limits are not authorized by REA.

Project / product Applicable terms and distinction
IDA Pro and Hex-Rays decompilers Proprietary Hex-Rays software governed by the EULA, purchase agreement, and applicable license scheme. Obtain rights for the required product, user, machine, decompiler, and automation interfaces. Availability of an API or a bridge does not grant hosting, service, or additional-user rights.
ida-pro-mcp The bridge's MIT license belongs to Duncan Ogilvie. It licenses the bridge code, not IDA or Hex-Rays products. Its README requires IDA Pro and explicitly states that IDA Free is unsupported. Follow the prerequisites for the version you actually install. The bridge is separately supplied, not bundled by REA.
Hopper Disassembler Proprietary Cryptic Apps software under its license agreement. Personal and computer licenses have different permitted-user and installation rules; an official evaluation trial is available. REA setup may obtain the official installer after approval, but this grants no paid license or activation entitlement.
JEB Proprietary PNF Software product under its EULA and edition-specific agreement. Check user/seat/server rights and whether your edition permits automation, backend/service integration, and disclosure of generated output. The published EULA restricts public or third-party disclosure of decompiled code, reconstructed artifacts, and analysis reports unless expressly permitted by the license type.

The vendor's applicable agreement controls. These summaries do not interpret your individual contract or expand the rights it grants. Verify permissions before publishing analysis output, sharing tool access, or operating a service. Vendor terms above were checked on 2026-10-12.

Runtimes, development tooling, and fixtures

REA uses a caller-supplied Node.js runtime (MIT and component notices). Optional workflows may also use Python (PSF and component licenses), OpenJDK (GPLv2 with Classpath Exception and component notices), Electron (MIT and component notices), or a Chromium-based browser (BSD-3-Clause and third-party licenses). These external installations are not licensed or bundled by REA's MIT license.

Development, test, and website npm packages are included in the locked inventory. GitHub Actions, operating-system utilities, downloaded verification fixtures, and their runtimes retain the terms supplied by their publishers. Fixture identities and provenance are recorded under scripts/fixtures/ and the existing third_party/ records; downloaded executable fixtures are not tracked or included in the npm package. This notice does not claim to inventory every dependency of a caller's operating system, agent, or separately installed tool.

Maintaining and redistributing notices

Refresh the dependency inventory and runtime notice collection when the lockfile changes. Review the actual versions and distributed contents, retain the upstream license and copyright texts, and account for optional platform packages. See licenses/README.md for source provenance, collection scope, and known upstream notice gaps.

The npm package includes this document, the licenses/ directory, and the existing redistributed license records under third_party/. If you additionally bundle an external engine or modify upstream code, review that actual distribution and retain its full applicable licenses, copyright notices, NOTICE files, modification notices, and source obligations. REA's inventory is not a substitute for those obligations.