c1fd496e6a
* feat(kuna): serve procedures, pseudocode and assembly from Kuna exports Register Kuna as a bring-your-own deep-analysis provider. It answers list_documents, list_procedures, search_procedures, procedure_address, address_name, procedure_pseudo_code, procedure_assembly and analyze_function (and batch_decompile through composition) from the verified project export. While a cold export builds in the background, pseudocode comes from a single-function `kuna decompile` run on a private copy and says so; assembly and data names wait for the export. Each answer records its source and file span in raw_result, limitations are scoped per operation, and the session-owned export is stopped on close unless another session still waits for it. The literal/regex procedure search predicate moves from the IDA runner into a shared domain helper. `npm run verify:kuna` adds a real-provider lane with an optional Ghidra comparison. Refs #1957 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(kuna): refuse a Ghidra comparison without caller-built targets Refs #1957 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(kuna): retry owned cleanup and keep answers bound to the opened Kuna - Re-verify the Kuna executable's digest before every launch (memoized by file identity), so no answer names one build while another produced it. - Keep the process supervisor of an unproven stop, and retry it on every later close in both the session and the cache; a failed close keeps failing until the stop is proven instead of reporting success. - Report an abandoned export's retained cleanup from session close. - Forget and rebuild an adopted export whose files another REA process evicted, instead of failing every later read. - Close a private copy whose setup failed, and retry failed removals. - Let the session own the shared quick inventory; each caller only stops waiting when it cancels. - Report a failed export as `failed` with its reason. - Lane: release the MCP client when open_binary rejects a target, and accept either valid source for the first answer. Refs #1957 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(kuna): drain session requests before releasing workspaces Combine caller cancellation with session shutdown and wait for active reads before releasing their process supervisors or private inputs. Retain unproven cleanup for later close attempts. Measure UTF-8 reply bytes without implying model token usage. Co-authored-by: gensokyo-dev <342580529+gensokyo-dev@users.noreply.github.com> Co-authored-by: Kaoru0822 <208281322+kaoru0822-kitauji@users.noreply.github.com> * perf(kuna): keep document metadata reads free of target analysis Listing the selected path no longer initializes the project cache or starts an export that the request never consumes. Co-authored-by: gensokyo-dev <342580529+gensokyo-dev@users.noreply.github.com> Co-authored-by: Kaoru0822 <208281322+kaoru0822-kitauji@users.noreply.github.com> * fix(kuna): reject verification matrices with missing functions Validate requested matrix coverage before building the fixture or opening providers. Empty matrices, unmatched names and partially matched function sets must fail instead of reporting an unperformed comparison as successful. Co-authored-by: gensokyo-dev <342580529+gensokyo-dev@users.noreply.github.com> Co-authored-by: Kaoru0822 <208281322+kaoru0822-kitauji@users.noreply.github.com> * fix(kuna): retain component provenance in function dossiers Record each source facet as one file span and preserve both pseudocode and assembly digests/ranges in combined reports. Keep direct text source fields compatible and verify every combined span through the real MCP lane. Co-authored-by: gensokyo-dev <342580529+gensokyo-dev@users.noreply.github.com> Co-authored-by: Kaoru0822 <208281322+kaoru0822-kitauji@users.noreply.github.com> * fix(kuna): keep retired file cleanup bound to its export Retain the export key with each failed file removal so a cancelled session reports and retries its own stopped resources. Preserve that association across sweeping and process-cleanup recovery without attributing unrelated cache failures to the session. Co-authored-by: gensokyo-dev <342580529+gensokyo-dev@users.noreply.github.com> Co-authored-by: Kaoru0822 <208281322+kaoru0822-kitauji@users.noreply.github.com> * docs(kuna): document the Kuna provider and list it in the catalog (#3855) * docs(kuna): document the Kuna provider and list it in the catalog Add the Kuna provider guide (configuration, answered tools, cold and warm paths, provenance, cache ownership, verification lane), link it from the README and its translations, the CLI, installation and index pages and the site navigation, describe `npm run verify:kuna` in the testing guide, credit Kuna in THIRD_PARTY_NOTICES, teach the agent skill when to select Kuna, and register its identity and operations in the generated product catalog. Refs #1957 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs(kuna): state the Linux cache fallback, raw_result scope and comparison inputs Refs #1957 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs(kuna): note that cache pins hold within one REA process Refs #1957 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs(kuna): describe retired staging and retried cleanup Refs #1957 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> * fix(kuna): supervise regex and bind reads to one export Share a cancellable ECMAScript matching worker with Hopper while preserving its error contract. Bind C and assembly indexes to immutable project readers, retry whole dossiers after eviction, and enforce the existing buffered-text capacity before allocating cached spans. Document the verified Linux scope and keep complete exports accessible. Co-authored-by: gensokyo-dev <342580529+gensokyo-dev@users.noreply.github.com> Co-authored-by: Kaoru0822 <208281322+kaoru0822-kitauji@users.noreply.github.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: N0zoM1z0 <161784452+N0zoM1z0@users.noreply.github.com> Co-authored-by: gensokyo-dev <342580529+gensokyo-dev@users.noreply.github.com>
24 KiB
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. |
| 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 12.1.4. Copies of its 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.833 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.