Skip to main content
← Back home

Open-source components

Last updated: September 1, 2026

Websites we build incorporate open-source software written by other people. Our client agreements require us to identify those components and the licence each one carries. This page is that schedule, published so any client can read it at any time without asking us for it.

Every component listed here is permissively licensed. None carries a fee, and none obliges a client to publish their own source code or to license their site to anyone else. In practice this list changes slowly, and only when we upgrade a site’s foundations.

Served as part of the site

These run in the finished website. Versions are given as the release line rather than an exact number, because patch updates ship as part of ordinary maintenance.

Components served as part of the site
ComponentVersionLicence
next14.2.xMIT
react18.3.xMIT
react-dom18.3.xMIT
@radix-ui/*1.xMIT
lucide-react0.4xxISC
tailwindcss3.4.xMIT
tailwind-merge2.xMIT
clsx2.xMIT
autoprefixer10.xMIT
postcss8.xMIT

Used to build the site

These run on our machines while a site is being built and tested. They are never delivered to anyone visiting the finished site.

Components used to build the site
ComponentVersionLicence
typescript5.xApache-2.0
eslint8.xMIT
eslint-config-next14.2.xMIT
@types/node20.xMIT
@types/react18.3.xMIT
@types/react-dom18.3.xMIT

Typefaces

Typefaces are chosen per project, so they vary from one site to the next. We use faces published under the SIL Open Font License 1.1, and we self-host them at build time rather than requesting them from a third-party server while a visitor is on the page. The specific faces used on a given site are listed in that client’s own schedule.

What this means for a client

Nothing is owed to any of the projects above, and nothing here restricts what a client may do with their finished site. The reason the list exists is narrower than it looks: our agreements draw a line between what we wrote and what we assembled, and this is the list that makes that line specific rather than theoretical.

A client’s own schedule, naming the exact versions and typefaces in their build, is provided with their agreement and updated if the stack changes materially. If you are a client and would like a fresh copy, ask and we will send one.

Third-party services

Some sites connect to services a client already pays for, such as a job-documentation system, a booking tool, or their Google Business Profile. Those are the client’s own accounts under the client’s own terms with the provider. They are not components of what we deliver, and they are named in the client’s schedule rather than here.

Questions about this page can go to info@advocate1917.com.