Repository navigation
Ship third-party license notices with the client - #61
Merged
Merged
Conversation
The client build writes THIRD_PARTY_NOTICES.txt into client/dist, listing each npm package bundled into the client with its license text and source. Packages without a license file get the standard text from client/licenses/.
markbackman
force-pushed
the
mark/third-party-notices
branch
from
September 28, 2026 19:19
c017ac6 to
fa84791
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Prebuilt wheel ships a Vite-built React client that bundles code from about 70 npm packages. Their licenses (MIT, Apache-2.0, BSD, ISC, OFL for the Geist font, and LGPL-2.1 for libav.js) require their notices to travel with that code, and the wheel didn't include any. This generates a notices file on every client build.
THIRD_PARTY_NOTICES.txttoclient/distwith each package's name, version, license, source link, and license text. The publish workflows already copyclient/distinto the wheel, so it ships without packaging changes. The list follows the dependencies, so it stays current as they change.@libav.js/variant-opus-af, and a few others) publish no license file. For those, the plugin uses the standard text fromclient/licenses/, taken from SPDX's license list (GNU for LGPL-2.1), with a copyright line pointing to the package's source.@pipecat-ai/moq-transportas a software Opus fallback for browsers without WebCodecs. It's listed with its LGPL-2.1 text and source repository. It stays a separate lazy-loaded file, so it can be replaced as the LGPL requires.