Skip to content

License Change Notice #1069

Open
Open

Description

@xiaochunjimmy

License Change Notice

Remix Icon has updated its license to Remix Icon License v1.0.

This update is intended to provide clearer and more practical usage boundaries,
while keeping Remix Icon free for both personal and commercial use.

What has not changed?

  • You can continue using Remix Icon in websites, apps, software, and commercial products
  • You can modify and integrate icons freely
  • Attribution is still optional

What is clarified?

  • Remix Icon may not be sold as standalone icon products or icon packs
  • Remix Icon may not be used as the primary value of a paid product
  • Remix Icon may not be used as logos, trademarks, or brand identities
  • Creating competing icon libraries based on Remix Icon is not allowed

This change does not affect normal usage in apps, websites, UI kits, templates,
or other products where icons are a supporting element.

Why Update the License?

Previously, we used the Apache-2.0 license and included some additional supplementary terms on top of it.

However, these additions created conflicts with the original Apache-2.0 license itself, which caused confusion among many of our users regarding the terms. This update is primarily intended to clarify the content of our license.

If you have questions about specific use cases, feel free to contact us.

Activity

  1. xiaochunjimmy commented on Jan 25, 2026

    @xiaochunjimmy
    MemberAuthor

    If you have any other questions regarding our license, please feel free to express your thoughts here.

    We will discuss them thoroughly and may make adjustments based on the content of our discussion.

  2. Rugvip commented on May 20, 2026

    @Rugvip

    Hello @xiaochunjimmy! 👋

    Wanted to put on your radar that this has affected our usage of @remixicon/react in the Backstage project. The new license is incompatible with the CNCF's pre-approved licenses and policy and we are not able to get an exception for the license. We are currently staying on the 4.8.0 version of the library, but we don't consider this viable long-term. The main option for us at this point is to move to a different library, but I would love to find a different solution. I wonder if you are open to considering any other licensing options that would be compatible, or generally finding a solution?

  3. xiaochunjimmy commented on Jun 1, 2026

    @xiaochunjimmy
    MemberAuthor

    @Rugvip Hi, How would you like me to cooperate? So that we can find a common solution?

  4. aantusahaa commented on Sep 10, 2026

    @aantusahaa

    Hi @xiaochunjimmy, thank you for providing this clarification.

    I maintain svelte-remixicon, a free and open-source Svelte integration for Remix Icon.

    The package:

    • generates one Svelte component for each Remix Icon;
    • embeds the SVG path data in those components;
    • distributes the complete icon set through npm;
    • does not create or market an alternative icon design;
    • is intended only to let Svelte users consume Remix Icon through native Svelte components;
    • is not sold or otherwise monetized.

    The wrapper code is currently published under MIT, and the latest release uses Remix Icon 4.9.1. I am reviewing the package metadata and notices following the license change.

    Could you please clarify:

    1. Is a framework-specific package like this considered a prohibited “competing icon library or icon set” under Section 3.2, or is it a permitted integration?
    2. If it is permitted, may my original Svelte wrapper code remain MIT while the Remix Icon artwork remains governed by Remix Icon License v1.0, as described in Section 9?
    3. What license files, npm license value, and README notices should the package include?

    Clarification on this would also help maintainers of similar framework integrations understand the intended boundary.

    Thank you.

  5. xiaochunjimmy commented on Sep 13, 2026

    @xiaochunjimmy
    MemberAuthor

    Hi @aantusahaa I think you can continue using your current license agreement; your project has not violated our agreement.
    For specific information, perhaps your Agent can tell you; from our perspective, there is no problem.

  6. llimeht commented on Sep 29, 2026

    @llimeht

    Hi @xiaochunjimmy! These icons have been included in useful modules like python-qtawesome which make them easy to use in other projects, which is great. Those projects end up in distributions like Fedora, Debian, Ubuntu etc... and as a result there are very clear rules about what is an acceptable licence for inclusion. We can't accept licences that are a potential trap for people who redistribute what we make and we can't accept licences that have reduced rights for some users.

    I understand why you have written a new licence and why you have included each clause in it - it's a natural desire to keep your own branding and recognition strong. However, that detracts from the wider free software movement which is about sharing and cooperation. I often discuss licences with academics who have written code and want to write their own licence for the same reasons you highlight - my advice to them is always to pick an existing licence that places like Fedora or Debian accept, because it saves everyone a lot of heartache getting the licence right and arguing about the clauses. Reading through your licence, BSD-3-clause, CC-BY-SA or Apache 2.0 all seem to capture the main intent.

    Looking specifically at the Debian Free Software Guidelines in comparison to The Remix Icon Licence v1.0,

    • §3 Restrictions: basically all of this clause is problematic:
      • §3.1 is a restriction on free redistribution (DFSG§1) and derived works (DFSG#3); likewise §2.3
      • §3.2 is a restriction on derived works (DFSG#3) and is very problematic for downstream usage in places like python-qtawesome and Debian packages where we would often need to patch files for the purposes of integration. This clause will also become problematic for Remix itself some time when you get busy, bored, or lose access to your github account for some reason ... no-one is allowed to just fork the project under a new name and keep it going
      • §3.3 is a restriction on use (DFSG#6); I get why you want it, but once we start micromanaging usage of individual parts of packages, there's no nice way of giving people free software.
    • §4 is somewhere between restrictions on usage and unneeded; the Remix licence doesn't need to tell people how to act responsibly with trademarked materials. I think §4.1 and 4.2 could just be deleted.
    • §9 highlights how problematic §3 and §4 are.
    • I expect that the people in Debian who have the final say on licence suitability would also say that much of §2 contradicts §3... at the point where parts of a licence seem to contradict themselves, they normally say "the whole licence is invalid, therefore we probably have no rights to distribute this work".

    (I also note that the previous licence of Apache 2.0 + the non-sale clause was also not DFSG-free and was also problematic, just that no-one had yet spotted the problem.)

    The bottom line is that the Remix 1.0 licence will cause all of the remix-related files to be stripped from packages in Debian, Ubuntu, Fedora etc, including versions that might be embedded in other projects like python-qtawesome; there's a good chance of that breaking projects that use python-qtawesome (there are quite a few) and we have no nice way of figuring that out in advance. I don't think anyone wins with that outcome. However, now that this problem is evident, I will probably need to act on it within the next couple of weeks in Debian (autoremoval of python-qtawesome and packages depending on it is currently scheduled for Oct 9).

    Thanks for your willingness to discuss the licencing of Remix - please let me know if I can offer any further information on this downstream perspective.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions