#10902·unleash

Self-host Sen font instead of using Google Fonts

Author: rmc47Created Oct 31, 2025Updated Nov 12, 2025
Labelsenhancement

Describe the feature request

Currently, the Unleash front-end loads the Sen font via Google Fonts (https://github.com/Unleash/unleash/blob/main/frontend/index.html#L17). This happens on all pages, including the login page.

As a result, public security scanners notice the lack of SRI integrity hash on this external resource, and can flag it as a finding.

Google Fonts' CDN doesn't support SRI (because they have some user-agent based dynamic logic) so it's not possible to add a hash to the current externally-hosted resource.

The Sen font is subject to the OFL, which allows free redistribution.

Given the performance benefits of using an external CDN are likely to be small (the Unleash HTML frontend is unlikely to see huge amounts of external visitors), would it be possible to include the font asset with Unleash, avoiding the external resource and SRI issues, and removing another external source from the CSP at the same time?

Background

Described above.

Solution suggestions

Include a WOFF2 version of the Sen font as a static asset distributed with the Unleash server, and serve this ourselves instead of referencing a CDN-hosted version.