External Publication
Visit Post

Epyrus • Re: Unclear about the License

Pale Moon forum - Forum index [Unofficial] May 21, 2026
Source

Also, while looking at Pale Moon's LICENSE file, I noticed a few odd things:

This URL doesn't seem to lead to anything: http://www.palemoon.org/licensing.shtml

And it also fails to note that toolkit/content/license.html is in the platform directory with UXP, rather than in the Pale Moon directory with the application itself. So that's already a couple of things I will have to revise when it comes to using that for Epyrus.

Thanks for reminding me about this. I've updated it to fix the references

For our code base, the platform is a mixed license situation with a mix of compatible copyleft licenses, primarily the MPL 2.0 (I've explained some things on the website in https://www.palemoon.org/legal.shtml) with a smattering of Apache, MIT, BSD and other licenses throughout, also dependent on how the base was configured when building, which wis why in general it's better to not use a legacy plaintext LICENSE file but rather the internal about:license schema in a compiled binary to get a better overview for a final application, although the more complete license with all the conditionals is of course better if you're asking purely about the source code license.

By the way, Athenian, if you need help writing licensing text, just ask.


Discussion in the ATmosphere

Loading comments...