TagBuilder Legal
Third-Party Notices
Review the attribution and licensing details for the libraries, fonts, and services that power the TagBuilder experience.
Third-Party Notices
TagBuilder incorporates the following third-party assets and dependencies. This notice summarizes where each component is used and the licensing obligations that accompany our distributions so all required attributions travel with the product.
Front-End Assets
| Asset | Where it is Used | License & Attribution Notes |
|---|---|---|
| Tailwind CSS | Bundled stylesheet generated with the official Tailwind CLI; the CDN script is only referenced for local development on localhost. |
Distributed under the MIT License. Include the MIT notice in documentation or release bundles; no on-page credit is required. |
| Inter font (Google Fonts) | Served through Google Fonts for primary typography. | Licensed under the SIL Open Font License 1.1. Retain the OFL text with any redistribution of the font files. |
Google tag (gtag.js) |
Embedded analytics snippet that loads on every page. | Governed by the Google Analytics Terms of Service. Ensure the Privacy Policy discloses this integration and explains opt-out options. |
static/js/qrcode.min.js |
Client-side helper that powers QR code generation in the builder. | Forked from the davidshimjs/qrcodejs project (MIT License). Preserve the upstream license notice alongside the bundled script. |
The first three assets are configured in templates/base.html, while the QR code helper resides at static/js/qrcode.min.js.
Python Dependencies
All backend packages are listed in requirements.txt and ship under permissive licenses such as MIT, BSD, Apache 2.0, ISC, MPL 2.0, or LGPL with exceptions. When distributing binaries or container images, include the corresponding license texts. Key considerations include:
- certifi (MPL 2.0): Keep a copy of the Mozilla Public License with any redistribution.
- Apache-licensed packages (e.g., requests): Retain copyright statements and the Apache 2.0 license text.
- psycopg2-binary (LGPL 3 with exception): If distributing compiled artifacts, include the license and note the provided linking exception.
Compliance Checklist
- Bundle this notice file and a
LICENSES/directory containing the referenced license texts with production releases. - Confirm the Privacy Policy documents the Google Analytics integration and provides opt-out guidance.
- Review future third-party additions against this checklist before deployment to maintain accurate attributions.