External TeX packages and document fonts

LuaBill uses the following independently developed software when creating business documents. The TeX engine, packages and document font files are supplied by the user's TeX distribution or operating system; these files are not included in the LuaBill source archive or Windows installer. Their licenses remain separate from LuaBill's Apache License 2.0.

This list records the direct class and package declarations in LuaBill.tex. Packages also load their own dependencies. The installed distribution's package information, source files and notices identify the precise versions and terms used on a particular computer. The links below lead to upstream source, documentation, author and license information.

Engine and distribution

Direct LaTeX packages

LPPL means the LaTeX Project Public License. The version indicated in each installed package controls; a package's source and documentation may have different terms.

Package / source and license informationRole in LuaBillUpstream authors or maintainersLicense family
article class / LaTeX baseDocument structure and standard text symbols (textcomp)The LaTeX Project Team and contributorsLPPL
fontspecUnicode and OpenType font selectionWill Robertson, Khaled Hosny, The LaTeX Project TeamLPPL
fontawesomeThe VAT verification check icon (\faCheck)Xavier Danaux; icon font by Dave GandyLaTeX package: LPPL; icon font: SIL OFL 1.1
babelDocument language and typesetting conventionsJohannes L. Braams, Javier Bezos and contributorsLPPL
csquotesQuotation support available to the templatePhilipp Lehman, Joseph WrightLPPL
geometryPaper size, margins and reserved footer spaceHideo Umeki, David Carlisle, The LaTeX Project TeamLPPL
PGF / TikZQR drawing, signature/stamp placement and folding marksTill Tantau and the PGF/TikZ TeamCode: GPL / LPPL options; manual: GNU FDL
fancyhdrPage headers and footersPieter van OostrumLPPL
enumitemRemarks and list layoutJavier BezosMIT
hyperrefClickable contact/legal links and PDF featuresSebastian Rahtz, Heiko Oberdiek, Oberdiek Package Support Group, The LaTeX Project TeamLPPL
xcolorDocument and table colorsUwe Kern, The LaTeX Project TeamLPPL
soulUnderline support available to the templateMelchior Franz, Heiko Oberdiek, Oberdiek Package Support GroupLPPL 1.3c or later
colortblColored item-table cells and rulesDavid CarlisleLPPL
lastpageTotal page count in the footerJeffrey Goldberg, Hans-Martin MünchLPPL
textposRecipient window and QR block placementNorman GrayLPPL
luacodeLua execution inside the templateManuel Pégourié-GonnardLPPL
ltablexFlexible-width item tables with page breaksAnil Goel; copyright QNX Software Systems Ltd.LPPL
draftwatermarkDraft watermarkSergio CallegariLPPL
eso-picPage overlay for folding marksRolf NiepraschkLPPL

Fonts used in generated documents

LuaBill.tex chooses the first available family in this order: Noto Sans, DejaVu Sans, Arial. The selected installed font is embedded or subset by the document tools. The Font Awesome icon font is selected separately by the legacy fontawesome package.

Font / primary license informationAttribution and termsHow LuaBill uses it
Noto SansThe Noto Project Authors; SIL Open Font License 1.1Preferred body font, when installed
DejaVu SansBitstream Vera copyright and license; DejaVu changes in the public domain; applicable Arev noticesFirst fallback, when installed
ArialMonotype typeface; separately licensed font. See Microsoft's font licensing and embedding FAQ.Final system-font fallback; the font files are not redistributed with LuaBill
Font Awesome 4 / fontawesome-latexIcon font by Dave Gandy; SIL OFL 1.1. The Font Awesome 4 upstream licensing notice distinguishes font and code licenses.Check icon; supplied by the external TeX package, not a LuaBill-authored icon

Ghostscript PDF/A integration and color profile

For ZUGFeRD, the runner calls the independently installed Ghostscript executable and sends it a short PostScript pdfmark configuration that defines an ICC output intent. This follows the interface described in the official Ghostscript PDF/A documentation. Ghostscript also supplies a sample configuration, PDFA_def.ps. The standard PDF keys and pdfmark operators are an integration interface; their appearance alone does not establish the origin or authorship of a program.

The runner obtains srgb.icc from that Ghostscript installation, or from the explicit LUABILL_ICC setting. It copies the profile to the document's working directory and uses it in PDF/A output. LuaBill's distributed sources and installer do not contain this external profile. The Ghostscript 10.05.1 profile inspected during this audit identifies itself as Artifex Software sRGB ICC Profile and carries Copyright Artifex Software 2011 in its embedded copyright tag. That observation identifies the inspected file, not all profiles that users may supply.

The profile and external program retain their own terms; they are not licensed as LuaBill's Apache-2.0 work. Ghostscript's official licensing information describes its AGPL and commercial options. The International Color Consortium profile library explains that an ICC profile's owner and terms are normally recorded in its metadata. The terms of a replacement profile must be checked with its provider.

Scope of the source review

The review covered the active LuaBill Lua, TeX and Python sources and direct dependencies. Beyond qrencode.lua, already credited to the luaqrcode project, it did not identify another vendored source module with a third-party authorship header. The absence of such a header does not prove that every historical snippet was originally written for LuaBill. Preserve any additional source or attribution information if the original authors supply it.

For bundled application libraries and Mustang CLI, see LICENSING.md, WINDOWS_NOTICES.md and the installed third-party-licenses directory. This document is an attribution and dependency inventory; the upstream license texts control.