Fomantic / Semantic UI assets in MicroPayments 4.0.0 ================================================== UI JavaScript and CSS: Fomantic UI 2.8.8, MIT license. Existing copyright headers and the accompanying MIT LICENSE are retained. Human-readable source: https://github.com/fomantic/Fomantic-UI/tree/2.8.8/src https://github.com/fomantic/Fomantic-UI/blob/2.8.8/dist/semantic.js https://github.com/fomantic/Fomantic-UI/blob/2.8.8/dist/semantic.css Build tools and license: https://github.com/fomantic/Fomantic-UI/blob/2.8.8/package.json https://github.com/fomantic/Fomantic-UI/blob/2.8.8/gulpfile.js https://github.com/fomantic/Fomantic-UI/blob/2.8.8/LICENSE.md Build upstream outside the WordPress runtime ------------------------------------------ 1. Clone https://github.com/fomantic/Fomantic-UI.git and check out tag 2.8.8. 2. Install its npm dependencies. The package's install script runs gulp install; follow its setup prompts to create semantic.json if necessary. 3. Run npm run build (the version's declared command is gulp build). This builds CSS, JavaScript and assets to the output configured in semantic.json. 4. Apply the exact CSS privacy patch below. Copy only the reviewed compiled runtime files into the plugin; do not ship node_modules, npm tooling or a development checkout. Keep this plugin's existing pinned font assets. The historical upstream package declares Node >=10.15.3 and npm >=6.4.1. Those are upstream build metadata, not a recommendation to run unsupported Node versions on production hosting. An isolated compatible build toolchain must be qualified if rebuilding. A full npm rebuild was not run for this privacy-only patch; the existing CSS and JS matched upstream distribution bytes before the explicit patch. The patch itself is reproducible directly from the tagged dist/semantic.min.css, without executing npm scripts. Exact CSS privacy patch ----------------------- Input: tagged dist/semantic.min.css SHA-256: 724060da937d645f4a3e7faf634d095c091da84d67bf6d2218cda1699842065e Remove exactly one occurrence of: @import url(https://fonts.googleapis.com/css2?family=Lato:ital,wght@0,400%3B0,700%3B1,400%3B1,700&subset=latin&display=swap); Then replace every expression matching this regular expression with none: url\(https://twemoji\.maxcdn\.com/[^)]+\) Expected replacements: 3057. Output: this directory's semantic.min.css SHA-256: 39510800f06a19ee59358e421afaec54341fab4cde7061f4c1ed3eba60a4cdf7 The MIT header and all selectors/other declarations are retained. There are no remaining remote CSS url() references in this patched file. Typography uses the CSS's locally available fallback fonts rather than fetching Lato. Conditional em[data-emoji] CDN backgrounds are disabled, so those empty markup-only emoji elements do not acquire replacement artwork. Use actual Unicode emoji text for native browser/system rendering in custom content. This patch does not inject an automatic emoji fallback or bundle Twemoji art. Existing textual Unicode emoji is unaffected. Pinned local fonts and images ----------------------------- The 16 existing font files are retained unchanged and exactly match the Semantic UI 2.3.3 distribution, rather than Fomantic 2.8.8's newer font set: https://github.com/Semantic-Org/Semantic-UI/tree/2.3.3/dist/themes/default/assets/fonts The legacy icons.otf also exactly matches Font Awesome v4.3.0. Webfont family metadata identifies Font Awesome 5 Free / Brands. See the authentic notices, full SIL OFL 1.1 text and copyright/source information in: themes/default/assets/fonts/NOTICE.txt themes/default/assets/fonts/Font-Awesome-LICENSE.txt themes/default/assets/fonts/OFL-1.1.txt Fonts retain their own license; the UI MIT notice does not relicense them. All referenced local CSS font/image paths are present. The retained older font map is not a claim that every glyph in newer Fomantic is available. Exact URLs, hashes, byte-match results and privacy patch counts are in asset-provenance.json. This is a reproducible source/license receipt, not an assertion that every upstream component or platform was requalified.