Which open-source projects changed their licence

Borehole reads each project's root licence file commit by commit. Of the 7 public projects in its library, 0 changed that licence in a way that changes what users may do. 0 of them narrowed it, and 0 now grant source-available terms, which are not open source. The counts move as the library grows.

What they grant now

Licence kind today	Projects
Permissive	0
Weak copyleft	0
Strong copyleft	0
Network copyleft	0
Source available	0

Every change, newest first

Project	Licence history	Now

Why a licence change matters in diligence

Code taken under the old terms stays under them. A buyer, a host or a fork may rely on either set, so both matter. A change toward source-available terms can restrict production use or offering the software as a service.

How this is counted

Each project counts once, from its newest public reading.
Only the root licence file counts, as it changed on the main line. A change on a branch counts when it lands.
A change that no release carried is set aside.
A move from one permissive licence to another is not counted: it changes nobody's rights in a way diligence weighs.
A change Borehole could not confirm from the history is left out.

Read a project, or your own

The library lists every project counted here.

Survey a repository: free on public repositories. Private code is read on your own machine by a collector whose source you can read first.