Draft prepared for attorney review. These documents are first drafts: they are not legal advice and have not been adopted by Varrock Inc. Points awaiting a business decision are marked [DECISION: …] and points for counsel [COUNSEL: …]; nothing here is in force.

Third-Party Notices — OasisGUI, oasis-runner, OasisNet and oasisgui.com

Draft prepared for review by counsel, dated 2026-10-06. This document is a first draft produced for attorney review and is not legal advice. It has not been adopted by Varrock Inc. The inventory was taken from the repository on that date (desktop app 2.0.0; bundled oasis-runner 0.47.0, oasisnet 0.1.0, oasis-vmhelper 0.9.0; helper manifest built 2026-09-30 from source commit 560a2901). Points that need a business decision are marked [DECISION: …]; points that need a lawyer's judgment are marked [COUNSEL: …]. All markers are collected in Section 13.

Related documents: End User License Agreement · Website Terms of Use · Privacy Policy · Acceptable Use Policy · Vulnerability Disclosure Policy · Index

1. Purpose, scope and method#

1.1 The software distributed by Varrock Inc. ("Varrock") contains and is delivered with software, firmware, fonts and data owned by others (the "Third-Party Components"). This notice identifies them, states each one's license, reproduces the notices those licenses require, and explains how Varrock meets the obligations attached to copyleft and proprietary components. Each Third-Party Component is licensed to you under its own terms, which prevail over the EULA for that component (EULA §6). This notice is informational. It grants no rights beyond those each component's own licence grants, and it is not a warranty that the inventory is complete. [COUNSEL: whether EULA §20.1 should incorporate this notice into the agreement or only refer to it; if incorporated, every marker must be resolved before publication and the published version frozen per release.]

1.2 Covered: every file in the OasisGUI installers for macOS (DMG), Linux (AppImage, .deb) and Windows (NSIS .exe), including the Helper Binaries listed under bundle.resources in src-tauri/tauri.conf.json, and the JavaScript served by oasisgui.com. Also covered: the Nix flake (flake.nix, nix/package.nix, nix/oasisnet-package.nix), which builds the Desktop App and Mesh Daemon from the repository source and copies every staged helper in src-tauri/binaries/ (including firecracker-*, which is not in bundle.resources; see Section 5). [DECISION: is the flake, and therefore the repository, publicly reachable? If so the source tree is already a distribution channel and must carry this notice and Appendix A, and the LGPL analysis in 9.1 and 9.3 changes because the vendored wireguard-control and src/spice/ are then distributed in source form.] Not covered: the Oasis Mobile app [DECISION: produce a mobile notice; OasisMobile/meshcore is MIT AND BSD-3-Clause and links the vendored boringtun]; build-only tools (Vite, esbuild, TypeScript, ESLint, lightningcss); software your own machine obtains at your instruction (Section 10).

1.3 Method. cargo metadata over the Rust workspaces src-tauri (869 packages), oasisnet (276) and runner (489), all targets and features; every third-party crate carries an SPDX expression and none comes from git. The union is 1,199 name@version rows (11 first-party) in scratchpad/research/meta/rust-inventory.tsv (the "Inventory"). Front end: package.json against node_modules (313 packages). Helper Binaries: src-tauri/binaries/manifest.json, scripts/fetch-*.sh and each pinned release's license files. Vendored trees: vendor/README.md.

1.4 Gaps. No notice file exists in the repository or any installer, and nothing regenerates one. [DECISION: adopt cargo about plus a Bun script to regenerate Appendix A per release, and decide where it surfaces — About dialog, this file, website /docs/, each installer.] [DECISION: enumerate the shared libraries inside a built Linux AppImage (linuxdeploy typically bundles GTK and WebKitGTK, LGPL-2.1-or-later) and add their notices; confirm whether libssl is bundled — openssl-sys is in the app graph without openssl-src, so it links the system OpenSSL unless the packager copies it in.]

2. Definitions#

• "Desktop App" (A): the oasis-gui executable and its React front end, bundled by Vite.
• "Runner" (R): oasis-runner, the daemon the Desktop App installs on each managed host.
• "Mesh Daemon" (N): oasisnet, the WireGuard mesh daemon, shipped as a separate executable.
• "Helper Binaries" (H): the third-party executables and firmware in manifest.json, shipped as application resources (Section 5).
• "Website" (W): oasisgui.com. The site published at the inventory date embeds no third-party JavaScript; it links the JetBrains Mono and Outfit web fonts from Google Fonts, which Google serves under the SIL OFL-1.1 and which Varrock does not distribute. The documentation build in the working tree (not yet published) bundles marked and mermaid and drops the Google Fonts link. [DECISION: confirm which site build is live when this notice is published.]
• "Statically linked": compiled into one or more of the shipped executables for its target. The Inventory is the union over all targets and features and therefore also lists build-time, test-only and other-platform crates (for example the Windows-only clipboard-win); Appendix A attributes them anyway. [DECISION: regenerate per shipped binary with cargo tree -e normal --target <triple> so Appendix A can say which executable contains which crate.] "Aggregated": shipped as a separate file and run as a separate process.

3. Component table, grouped by license#

Counts are distinct name@version pairs in the Inventory unless stated otherwise.

3.1 Permissive licenses (reproduce license text and copyright notice)#

3.2 Weak copyleft, file-scoped — MPL-2.0#

pariter 0.6.0 (R) offers MPL-2.0 as one of three options (MPL-2.0 OR MIT OR Apache-2.0); Varrock elects MIT, so it is not an MPL component.

MPL-2.0 attaches to the covered files only; static linking does not extend it (MPL §1.10, §3.3). Obligations: keep the MPL notices, include the MPL-2.0 text and make the covered files' source available (§3.2). Nothing is modified, so the upstream repositories above are the source. [DECISION: confirm upstream URLs as the §3.2(b) route and keep them current per release.]

3.3 LGPL#

3.4 GPL#

No GPL code is statically linked into any Varrock executable. The one GPL component shipped is the aggregated crun; see Section 9.2. No AGPL, SSPL, EUPL or CC-BY-SA component is shipped.

3.5 Proprietary components#

3.6 Fonts and data#

JetBrains Mono (four .woff2, src/assets/fonts/): SIL Open Font License 1.1, Reserved Font Name "JetBrains Mono". Symbols Nerd Font Mono (.ttf): MIT patcher plus each glyph source's license. No license file ships with either. [DECISION: add the OFL-1.1 text with the Reserved Font Name notice and the Nerd Fonts license bundle.] The CNN upscaler weights (src/cnnWeights.ts) are first-party, trained in-house (scripts/train_upscaler.py) on a synthetic dataset that scripts/gen_dataset.py renders from system fonts and procedural content; no external dataset is downloaded. [COUNSEL: whether rendering OS-bundled fonts into training images raises any font-licence question.]

4. Vendored components and local modifications#

BSD and MIT permit these modifications without publication. The modified LGPL files must be marked as modified and made available under their LGPL (Section 9). The ledger of every change is vendor/README.md.

5. Bundled Helper Binaries#

Each is pinned by SHA-256 in manifest.json; all but skopeo are upstream release binaries, skopeo is built by Varrock from unmodified upstream source. Firecracker is staged and hash-pinned but is not in bundle.resources (scripts/fetch-firecracker.sh says it is pushed to a host by vm_remote::install_helper), so the installers may not contain it while the Nix package copies it; [DECISION: state which channel delivers firecracker-* to hosts (installer resource, Nix package, or runner push from the developer stage) and add it to §1.2 accordingly].

6. Attribution text obligations#

6.1 Every binary distribution must carry: the license text and copyright for each 3.1 component; each Apache-2.0 NOTICE; the full MPL-2.0, LGPL-2.1, LGPL-3.0 (with GPL-3.0, which it incorporates) and GPL-2.0 texts; the OFL text and Reserved Font Name; WireGuardNT's LICENSE.txt; and the dual-license elections in 3.1, 3.3 and 3.4 plus dompurify 3.2.7 (MPL-2.0 OR Apache-2.0, elected Apache-2.0) and pariter 0.6.0 (MPL-2.0 OR MIT OR Apache-2.0, R, elected MIT). These form Appendix A, which does not yet exist. [DECISION: generate Appendix A mechanically and ship it as THIRD-PARTY-NOTICES.txt in each installer and in the About dialog.]

6.2 Firecracker NOTICE (Apache-2.0 §4(d)):

Firecracker Copyright 2017-2020 Amazon.com, Inc. or its affiliates. All Rights Reserved. SPDX-License-Identifier: Apache-2.0

Portions Copyright 2017 The Chromium OS Authors. All rights reserved. Use of this source code is governed by a BSD-style license that can be found in the THIRD-PARTY file.

The Firecracker release bundle includes libseccomp which is available under the LGPLv2.1 license. This is used in the Firecracker build process to produce cBPF bytecode that is shipped alongside Firecracker for use by the Linux kernel.

6.3 OpenSSL-derived attribution. ring and aws-lc contain code derived from OpenSSL and SSLeay whose licences require (i) that every redistribution retain the acknowledgments "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)" and "This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)" — Appendix A carries both — and (ii) that advertising materials mentioning features or use of that software display them. [COUNSEL: whether (ii) reaches Varrock's marketing of OasisGUI/OasisNet, and confirm against the shipped LICENSE files of ring 0.17.14 and aws-lc-sys 0.41.0/0.43.0 which OpenSSL/SSLeay portions survive in those builds; this draft has not checked them.]

6.4 Endorsement clauses. BSD-3-Clause holders (Cloudflare, Google, TianoCore and others) and WireGuard LLC forbid using their names to endorse or promote Varrock's products; marketing may name what the software uses only nominatively. [COUNSEL: review site copy such as "WireGuard underneath" (website/index.html:555) and "WireGuard's own signed driver" (website/index.html:622, 677, 1025) against §3(e) in Section 7 and any WireGuard trademark policy.]

7. WireGuardNT prebuilt driver — license statement, exactly as upstream#

7.1 The file wireguard.dll is byte-identical to bin/amd64/wireguard.dll in wireguard-nt-0.10.1.zip from download.wireguard.com. The Mesh Daemon's Windows backend (wgnt.rs) loads it only from its own directory and uses only the exports declared in wireguard.h (the "Permitted API"). Upstream's README states that the repository source is GPLv2 while the prebuilt binaries are under the following license, reproduced as transcribed (see the note following the text):

Prebuilt Binaries License

1. DEFINITIONS. "Software" means the precise contents of the "wireguard.dll" files that are included in the .zip file that contains this document as downloaded from download.wireguard.com.

2. LICENSE GRANT. WireGuard LLC grants to you a non-exclusive and non-transferable right to use Software for lawful purposes under certain obligations and limited rights as set forth in this agreement.

3. RESTRICTIONS. Software is owned and copyrighted by WireGuard LLC. It is licensed, not sold. Title to Software and all associated intellectual property rights are retained by WireGuard. You must not: a. reverse engineer, decompile, disassemble, extract from, or otherwise modify the Software; b. modify or create derivative work based upon Software in whole or in parts, except insofar as only the API interfaces of the "wireguard.h" file distributed alongside the Software (the "Permitted API") are used; c. remove any proprietary notices, labels, or copyrights from the Software; d. resell, redistribute, lease, rent, transfer, sublicense, or otherwise transfer rights of the Software without the prior written consent of WireGuard LLC, except insofar as the Software is distributed alongside other software that uses the Software only via the Permitted API; e. use the name of WireGuard LLC, the WireGuard project, the WireGuard project, or the names of its contributors to endorse or promote products derived from the Software without specific prior written consent.

4. LIMITED WARRANTY. THE SOFTWARE IS PROVIDED "AS IS" AND WITHOUT WARRANTY OF ANY KIND. WIREGUARD LLC HEREBY EXCLUDES AND DISCLAIMS ALL IMPLIED OR STATUTORY WARRANTIES, INCLUDING ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, QUALITY, NON-INFRINGEMENT, TITLE, RESULTS, EFFORTS, OR QUIET ENJOYMENT. THERE IS NO WARRANTY THAT THE PRODUCT WILL BE ERROR-FREE OR WILL FUNCTION WITHOUT INTERRUPTION. YOU ASSUME THE ENTIRE RISK FOR THE RESULTS OBTAINED USING THE PRODUCT. TO THE EXTENT THAT WIREGUARD LLC MAY NOT DISCLAIM ANY WARRANTY AS A MATTER OF APPLICABLE LAW, THE SCOPE AND DURATION OF SUCH WARRANTY WILL BE THE MINIMUM PERMITTED UNDER SUCH LAW. ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT THESE DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.

5. LIMITATION OF LIABILITY. To the extent not prohibited by law, in no event WireGuard LLC or any third-party-developer will be liable for any lost revenue, profit or data or for special, indirect, consequential, incidental or punitive damages, however caused regardless of the theory of liability, arising out of or related to the use of or inability to use Software, even if WireGuard LLC has been advised of the possibility of such damages. Solely you are responsible for determining the appropriateness of using Software and accept full responsibility for all risks associated with its exercise of rights under this agreement, including but not limited to the risks and costs of program errors, compliance with applicable laws, damage to or loss of data, programs or equipment, and unavailability or interruption of operations. The foregoing limitations will apply even if the above stated warranty fails of its essential purpose. You acknowledge, that it is in the nature of software that software is complex and not completely free of errors. In no event shall WireGuard LLC or any third-party-developer be liable to you under any theory for any damages suffered by you or any user of Software or for any special, incidental, indirect, consequential or similar damages (including without limitation damages for loss of business profits, business interruption, loss of business information or any other pecuniary loss) arising out of the use or inability to use Software, even if WireGuard LLC has been advised of the possibility of such damages and regardless of the legal or quitable theory (contract, tort, or otherwise) upon which the claim is based.

6. TERMINATION. This agreement is affected until terminated. You may terminate this agreement at any time. This agreement will terminate immediately without notice from WireGuard LLC if you fail to comply with the terms and conditions of this agreement. Upon termination, you must delete Software and all copies of Software and cease all forms of distribution of Software.

7. SEVERABILITY. If any provision of this agreement is held to be unenforceable, this agreement will remain in effect with the provision omitted, unless omission would frustrate the intent of the parties, in which case this agreement will immediately terminate.

8. RESERVATION OF RIGHTS. All rights not expressly granted in this agreement are reserved by WireGuard LLC. For example, WireGuard LLC reserves the right at any time to cease development of Software, to alter distribution details, features, specifications, capabilities, functions, licensing terms, release dates, APIs, ABIs, general availability, or other characteristics of the Software.

The text above cannot be diffed against the upstream file from the repository: scripts/fetch-wireguard-nt.sh extracts only wireguard-nt/bin/amd64/wireguard.dll from the zip and discards its LICENSE.txt and README.md. [DECISION: extend scripts/fetch-wireguard-nt.sh to also extract and stage the zip's LICENSE.txt and README.md, pin their SHA-256 in manifest.json, and diff this section against them at each regeneration; until then the three apparent typographical anomalies in the text above ("the WireGuard project, the WireGuard project" in §3(e), "legal or quitable theory" in §5, "This agreement is affected until terminated" in §6) are reproduced as found and have not been checked against the upstream file.]

7.2 Varrock relies on the §3(d) exception: the DLL is distributed only alongside oasisnet.exe, which uses it solely through the Permitted API. [COUNSEL: (i) §1 defines "Software" as the contents of the wireguard.dll files — contents unchanged, staged file name different; (ii) §3(e) and any WireGuard trademark policy; (iii) whether LICENSE.txt must be installed beside the DLL, which the installer does not do today.] [DECISION: install the upstream LICENSE.txt beside wireguard.dll.]

8. Microsoft Edge WebView2#

On Windows the Desktop App renders in the Microsoft Edge WebView2 Runtime, Microsoft software installed on your PC under Microsoft's license. The Windows installer embeds Microsoft's Evergreen Bootstrapper and runs it silently to install the Runtime if absent. Neither is licensed by Varrock. [COUNSEL: identify the exact Microsoft terms governing redistribution of the Bootstrapper and the Runtime's end-user license, and reproduce or link them verbatim; this draft deliberately does not paraphrase them.]

9. Copyleft components and how obligations are met#

9.1 LGPL-2.1-or-later — wireguard-control, statically linked into the Mesh Daemon. LGPL §6 applies to that executable only; the Desktop App and Runner do not contain the library. §6 requires prominent notice that the LGPL library is used, a copy of the LGPL, and a way to modify and relink: the library's complete source plus the source or object code of the proprietary parts sufficient to relink (§6(a)), or a shared-library mechanism (§6(b)). §6 also allows a written offer valid for at least three years (§6(c)) or a designated-place offer (§6(d)), and in every case requires that the Mesh Daemon's own licence terms permit modification of the work for the customer's own use and reverse engineering for debugging such modifications, and that the library's copyright notice and a pointer to the LGPL appear wherever the daemon prints its own. [COUNSEL: EULA §4.1(a) must carry an express carve-out for LGPL-covered debugging and relinking; §6.2(a) grants modify-and-relink only.] Current state: vendor/README.md says §6 is met "by making its full source (this vendor tree + oasisnet/) available to binary recipients", but no source is published through a channel that binary recipients are told about [DECISION: see §1.2 on the Nix flake], no written offer exists, the LGPL-2.1 text is in neither the vendor tree nor any installer, and the modified files are not marked (§2(b)). [COUNSEL: choose the §6 route — (a) publish vendor/innernet/wireguard-control, vendor/boringtun and oasisnet/ source (exposing the Mesh Daemon's own source), (b) relink as a shared object, or (c) replace the crate — and settle written-offer wording and its three-year term if route (a) is met by offer.] [DECISION: add COPYING.LESSER to vendor/innernet/wireguard-control/ and Appendix A; mark modified files.] Until then the EULA's statement that corresponding source can be obtained "as described in the Third-Party Notices" cannot be honoured, and this notice must not claim otherwise.

9.2 GPL-2.0-or-later — the crun executable. crun is an unmodified upstream executable that the Runner only runs as a child process; nothing of Varrock's is linked with it. Distributing it in binary form still triggers GPLv2 §3: the complete corresponding source accompanies the binary (§3(a)) or a written offer, valid for at least three years and open to any third party, accompanies it (§3(b)); §3(c) is unavailable to a commercial distributor. [COUNSEL: whether a pointer to upstream's repository can satisfy §3(a) for a distributor of binaries; and whether the Runner's hash-gated copy of crun onto managed hosts (scripts/fetch-crun.sh: "shipped to the host by the normal runner-deploy path") is a further distribution needing its own notice.] COPYING and COPYING.libcrun must ship. Current state: none of this is in place, and the static contents of upstream's release binary (libseccomp, yajl, libcap and others) are not inventoried. [COUNSEL: choose §3(a) (mirror crun 1.15 source and its static dependencies), §3(b) (written offer), or remove crun from bundle.resources so it is fetched only on hosts that need it.]

9.3 LGPL-3.0-or-later — spice-html5, minified into the front end. LGPL-3.0 §4 (Combined Works) applies. It requires, in addition to prominent notice and the LGPL-3.0 and GPL-3.0 texts: (d)(0) the Minimal Corresponding Source of the library as modified, and the Corresponding Application Code of the Desktop App's front end in a form and under terms that let the user recombine it with a modified library (§4(d)(0)), or a suitable shared-library mechanism (§4(d)(1)); (c) the library's copyright notice among any the app displays; and licence terms for the Desktop App that do not restrict modification of the library portions or reverse engineering to debug such modifications. The EULA must carry that permission — today §4.1(a) bars reverse engineering except as law permits and §6.2(b) grants nothing beyond a marker [COUNSEL: add to EULA §4.2/§6.2(b)]. For a minified bundle, (d)(0) therefore means shipping the un-minified src/spice/ with the Varrock patch and the front-end bundle in relinkable form with build instructions; (d)(1) means loading the library as a separate, replaceable script. [COUNSEL: choose the route — separate-chunk loading plus source, source publication of library and application code, or replacement with a non-LGPL SPICE client.] [DECISION: ship the two-line Varrock patch and src/spice/ as source, together with whatever application code the chosen route requires.]

9.4 MPL-2.0 is met by the notices and source pointers in 3.2. Dual-license elections (3.1, 3.3, 3.4, 6.1) must be stated in Appendix A.

10. Software that Varrock does not distribute#

On your instruction the software causes your own machines to obtain, directly from the publishers, software Varrock does not redistribute: Chromium (via your host's package manager); the Ubuntu cloud image, and the Ubuntu base and Alpine minirootfs tarballs used to build microVM root filesystems; a prebuilt Linux guest kernel for Firecracker microVMs, fetched from Firecracker's published CI artifacts; the redroid/redroid container image; Appium's prebuilt WebDriverAgent simulator bundle (iOS Simulator sessions on macOS); the Claude Code, Codex and Kimi command-line agents; tmux; podman or docker; and any model API you configure with your own credentials. Each is governed by its own terms. [DECISION: whether to document the guest kernel's GPL-2.0 status and source location in user docs, since Varrock pins it by checksum but does not distribute it.]

11. Trademarks#

WireGuard is a registered trademark of Jason A. Donenfeld. Microsoft, Edge and WebView2 are trademarks of Microsoft Corporation. Other names belong to their owners; no affiliation or endorsement is implied. [COUNSEL: confirm the trademark attributions that the component owners' policies require, for example for Firecracker and Cloud Hypervisor.]

12. Updates and contact#

12.1 This notice is accurate for the versions in the preamble and is to be regenerated with each release. Earlier releases carried no notice. [DECISION: whether to publish notices retroactively for earlier releases still offered for download.]

12.2 Source requests under Section 9 and questions about this notice go to [DECISION: contact mailbox — only sales@oasisgui.com exists today; do not invent a legal@ or oss@ address] and, for any written offer that must name a postal channel, to [DECISION: postal address for correspondence — the registered agent (LegalInc Corporate Services Inc., 131 Continental Drive, Suite 305, Newark, DE 19713, USA) is a service-of-process address only].

12.3 This notice is a licence and attribution record. It is not the software bill of materials required by Regulation (EU) 2024/2847 Annex I Part II(1); that SBOM is addressed in the EU Product-Compliance Memo §4.4 and is to be generated from the same Inventory data. [DECISION: have the Appendix A generator emit the SBOM (CycloneDX or SPDX) from the same run.]

Appendix A — License texts. [DECISION: to be generated mechanically per 1.4; the texts listed in 6.1 are required and not yet collected.]

13. Open decisions#

1. §1.1 [COUNSEL: whether EULA §20.1 incorporates this notice into the agreement or only refers to it; if incorporated, resolve every marker and freeze the published version per release.]
2. §1.2 [DECISION: separate notice for Oasis Mobile.]
3. §1.2, §9.1 [DECISION: is the Nix flake, and therefore the repository, publicly reachable? If so the source tree is a distribution channel that must carry this notice and Appendix A, and the LGPL route analysis changes.]
4. §1.4, §6.1 [DECISION: cargo about + Bun script to generate Appendix A per release; where notices surface; ship as THIRD-PARTY-NOTICES.txt.]
5. §1.4 [DECISION: enumerate AppImage .so files; confirm whether libssl is bundled.]
6. §2 [DECISION: confirm which website build (Google Fonts link, or the unpublished docs build bundling marked and mermaid) is live when this notice is published.]
7. §2 [DECISION: regenerate the Inventory per shipped binary (cargo tree -e normal --target <triple>) so Appendix A can say which executable contains which crate.]
8. §3.1 [COUNSEL: blanket MIT election for MIT OR Apache-2.0 crates, per-group elections inside compound AND expressions, and that Appendix A must state each election.]
9. §3.1 [COUNSEL: per-package notices for the edk2 firmware image.]
10. §3.2 [DECISION: upstream URLs as the MPL §3.2(b) source route.]
11. §3.3, §9.3 [DECISION: record the spice-html5 upstream commit; ship the patch and src/spice/ as source, together with whatever application code the chosen §4 route requires.]
12. §3.4 [COUNSEL: RocksDB Apache-2.0 election wording.]
13. §3.6 [DECISION: add OFL-1.1 with Reserved Font Name and the Nerd Fonts licenses.] [COUNSEL: whether rendering OS-bundled fonts into the CNN upscaler's synthetic training images raises any font-licence question.]
14. §4 [DECISION: record vendor/rustic pin and diffs.]
15. §5 [DECISION: state which channel delivers firecracker-* to hosts — installer resource, Nix package, or runner push — and add it to §1.2.]
16. §5 [DECISION: Go-module notice list for the self-built skopeo.]
17. §6.3 [COUNSEL: whether the OpenSSL/SSLeay advertising clause reaches Varrock's marketing; confirm against the shipped LICENSE files of ring 0.17.14 and aws-lc-sys 0.41.0/0.43.0.]
18. §6.4 [COUNSEL: site copy ("WireGuard underneath", "WireGuard's own signed driver") versus WireGuard §3(e) and trademark policy.]
19. §7.1 [DECISION: stage the WireGuardNT zip's LICENSE.txt and README.md, pin them in manifest.json, and diff Section 7 against them; the three apparent typographical anomalies are unchecked until then.]
20. §7.2 [COUNSEL: WireGuardNT renamed file versus "precise contents"; §3(e); whether LICENSE.txt must be installed beside the DLL.] [DECISION: install LICENSE.txt beside wireguard.dll.]
21. §8 [COUNSEL: reproduce verbatim the Microsoft WebView2 Bootstrapper and Runtime terms.]
22. §9.1 [COUNSEL: LGPL-2.1 §6 route for wireguard-control — publish source, relink dynamically, or replace; written-offer wording; EULA §4.1(a) carve-out for LGPL-covered debugging and relinking.] [DECISION: add COPYING.LESSER; mark modified files.]
23. §9.2 [COUNSEL: GPLv2 §3 route for crun — source, written offer, or drop from bundle.resources; whether a pointer to upstream can satisfy §3(a); whether the Runner's copy of crun onto managed hosts is a further distribution.]
24. §9.3 [COUNSEL: LGPL-3.0 §4 route for minified spice-html5 — separate chunk, source publication of library and application code, or replacement; add the §4 modification and reverse-engineering permission to EULA §4.2/§6.2(b).]
25. §10 [DECISION: whether to document the Firecracker guest kernel's GPL-2.0 status and source location in user docs.]
26. §11 [COUNSEL: trademark attributions required by component owners' policies.]
27. §12 [DECISION: retroactive notices for earlier releases.] [DECISION: contact mailbox for source requests — only sales@oasisgui.com exists.] [DECISION: postal address for correspondence in any written offer — the registered agent's address is for service of process only.]
28. §12.3 [DECISION: have the Appendix A generator emit the CRA SBOM (CycloneDX or SPDX) from the same run.]

Source: docs/legal/third-party-notices.md in the repository · draft for attorney review · 45 [DECISION] markers and 30 [COUNSEL] markers on this page.