Licences

TWO SEPARATE QUESTIONS; the second is open, which is why this is needs-verification rather than compliant. (1) THE MARKETPLACE ITSELF — clean. LICENSE (MIT) diffed byte-for-byte against upstream camthink-ai/NeoMind-Extensions via the GitHub API and confirmed identical, including the 'Copyright (c) 2026 CamThink Team' line, retained unmodified. MIT allows the CrowdSense rebrand so long as that notice survives, and it does. (2) THE meshtastic-bridge EXTENSION — unresolved, and NOT currently distributed. A previous pass recorded that it 'HAS now landed' and dismissed the copyleft question on the basis that it is 'a first-party, from-scratch Rust implementation' that 'does not vendor GPL-3.0 Meshtastic source'. Both halves are wrong. It is not on the default branch — `gh api .../contents/extensions/meshtastic-bridge` returns 404, and the published listing has 25 extensions, none of them this one; it exists only on `feat/meshtastic-bridge`. And its own source contradicts the from-scratch claim: `src/proto.rs` (640 lines) states in its module docstring that it is 'transcribed **verbatim** from the canonical protobuf definitions at github.com/meshtastic/protobufs@master (meshtastic/{mqtt,mesh,portnums,telemetry,paxcount}.proto)', carrying message names, field names and wire tags across, with 'Field numbers are load-bearing'. That upstream repo is GPL-3.0 (confirmed via the GitHub API), while this crate's Cargo.toml declares `license = "Apache-2.0"`. Whether transcribing protobuf schema definitions produces a derivative work is a real legal question and not one this manifest should answer either way — but it must be answered before that branch merges, because if it is derivative then the Apache-2.0 declaration conflicts with GPL-3.0 and §5(a) change-notice obligations attach. Nothing GPL-derived is distributed today, so this is a pre-merge condition, not a live violation.