License

License

TL;DR reveal-init belongs to the Public Domain and you are free to use it for any purpose without any condition.

As clearly stated in the README, reveal-init is licensed under The Unlicense. A copy of The Unlicense is included in the repository (see the file UNLICENSE). The terms of The Unlicense are also applied to other documents and code found within the reveal-init GitHub repository, excluding the copy of The Unlicense.

In some countries, however, The Unlicense's terms cannot be legally applied. If so:

I, the copyright holder of this work, grant you the right to use this work for any purpose without any condition, unless there exist conditions required by law. The software does not come with any warranty or liability.

The above statement is the written permission from the author and may be referred to as the "prior written permission" or any phrase that conveys the same meaning.

Under the effect of The Unlicense or the written permission, reveal-init is a dedication that belongs to the Public Domain. That means you are free to use the work for any purpose by any means, without any condition.

Issues concerning The Unlicense

Several issues arose around The Unlicense. When talking about its downsides, people often provide a link to this answer on Software Engineering Stack Exchange. While it is indeed that there are other public-domain-like licenses that are more highly recommended over The Unlicense, The Unlicense is still the preferred choice of license for reveal-init, because the statements made within the first 2 paragraphs are very straight forward and easy to be interpreted and understood:

This is free and unencumbered software released into the public domain.

Anyone is free to copy, modify, publish, use, compile, sell, or distribute this software, either in source code form or as a compiled binary, for any purpose, commercial or non-commercial, and by any means.

The written permission is also provided to close the issue around the license's illegality in certain countries.