Third-party notices

Third-party tools make the browser flasher possible.

The public Tagger-101 package uses third-party browser, firmware, and build tooling. This page identifies the public dependencies and references a builder may see while flashing or checking firmware provenance.

Runtime And Firmware Build Notices

ItemCredit / LicensePublic Use
ESP Web Tools 10.2.1 ESP Web Tools by the ESPHome maintainers, Apache License 2.0. Local license copy: Apache-2.0. The firmware flasher loads the audited 10.2.1 browser installer from UNPKG. Docs: ESP Web Tools. Source: GitHub.
ESP-IDF ESP-IDF by Espressif Systems. Most components are Apache License 2.0 with permissive third-party components. Local license copy: Apache-2.0. ESP32 firmware binaries are built with ESP-IDF. See the firmware provenance page for public artifact details.
Web Serial API Browser API, not a packaged project dependency. Used by ESP Web Tools after browser permission to communicate with connected ESP boards.

Project Assets

DIYLaserTag logo files, generated schematic SVGs, page layouts, and firmware manifests are provided as part of this website package. Do not reuse, rebrand, or republish them as another project's release package without permission.

Notice Scope

Local development scripts, build containers, private source trees, and node_modules are not included in the public static website unless they are explicitly bundled. This notice focuses on what ships to builders.

Protocol References

MilesTag II / MILES2-style IR packet behavior is referenced only as a protocol profile for selected shot behavior. DIYLaserTag firmware is not MilesTag firmware, is not certified by any third-party system owner, and does not guarantee compatibility with third-party game logic, equipment, accessories, or event rules.