Request: show the licence in the project page header, including when it has extra conditions

Site FeedbackJecika3 replies

JecikaMember#1

When scanning project pages the first two things I look for are "is it maintained" and "what licence". The fact block already answers the first (last commit date, activity within six months). The licence is only in the body text and sometimes only as the SPDX code.

Two requests:

  1. Put the licence next to stars and language in the header, as the SPDX identifier (MIT, Apache-2.0, AGPL-3.0, and so on). The data is already in the database; licenseSpdx is in the daily project snapshots.
  2. Mark the cases where the LICENSE file is not plain SPDX text: Dify's Apache-2.0-with-conditions, n8n's Sustainable Use License, Marker's weights terms, Open WebUI's branding clause. A small "additional terms" label with a link to the file would stop the "it says Apache" misunderstanding that the Open Source board already has a thread about.

The second one needs a human to read the file, so it cannot be fully automatic. But a flag on the handful of very popular projects where it matters would carry most of the value.

3 replies

Hysen YanStaff#2

Agree with both. The first is a template change and the field exists, so it can be quick. The second will be a reviewed field, set by hand on the pages where it applies, with the note shown to readers and a link to the LICENSE file at the commit we read. We will start with the projects named in this thread and in the Dify topic.

NicholasMember#3

Add a third category to the flag: "licence changed". A few projects moved licence in the last two years (Open WebUI is one), and a page that cites the old one is wrong in a way that matters to someone deploying today. Even a date on the licence line ("as read on 2026-10-09") would help.

EdenMember#4

Seconding the header placement. On mobile the fact block is below the fold, and the licence is the one thing I would want above it.

More in Site Feedback