Allowed Open Source License Policy for Safe Operation with Online Services and Client-Side Libraries from the OpenLibs.dev Catalog

We develop our own interactive web applications and user interfaces (UI) on top of popular Open Source solutions, without modifying the original source code of the libraries themselves. We strictly monitor the legal compliance of the components used, choosing only safe, permissive licenses. This guarantees 100% legal safety for both users of our services and developers who use our examples in their commercial projects.

For Users Applications
For devs Libraries

Quick License Compatibility Guide

License Admission Status Commercial Use Closure of Own Code (UI)
Unlicense Allowed Yes Yes (Full, unconditional)
MIT Allowed Yes Yes (Keep copyright)
Apache 2.0 Allowed Yes Yes (Keep copyright)
BSD-2-Clause Allowed Yes Yes (Keep copyright)
BSD-3-Clause Allowed Yes Yes (Keep copyright)
ISC Allowed Yes Yes (Keep copyright)
MPL 2.0 Conditional (Safe) Yes Yes (If module code is unchanged)
LGPLv3 Conditional (Safe) Yes Yes (With dynamic connection)
GPLv3 Forbidden With risk No (Requires opening the entire website)
AGPLv3 Forbidden With risk No (Full viral copyleft)
CC-BY-NC Forbidden With risk Not applicable (Not for commerce)

Frequently Asked Questions Regarding Licensing

Yes, it is 100% safe. We carefully select the tools and ensure they are based exclusively on permissive (MIT, Apache 2.0, BSD-2-Clause, BSD-3-Clause, ISC, Unlicense) or weak copyleft (MPL 2.0, LGPLv3) solutions. You can use the interactive examples in your own closed commercial developments without any hidden obligations.

The MPL 2.0 license requires code disclosure only if you modify the source files of the library itself. Since we develop custom user interfaces and wrappers (Wrapper UI Layer) on top of the libraries without touching their original code, the copyleft conditions are not activated. Your proprietary code remains completely closed.

In classic software, LGPLv3 requires dynamic linking of the library so that the user can independently replace its version. In client-side web, where code is compiled by bundlers (Vite, Webpack), this boundary is legally blurred. However, usage on OpenLibs.dev is completely safe: we do not integrate them into the core, but connect them as completely isolated external modules. Since the library's source code is not modified and your website interacts with it exclusively through an external API, the copyleft effect does not extend to your own work — the commercial code of the website remains 100% closed.
Client-Side Only Secure client-side code with no hidden obligations.

Permissive Licenses (Maximum Freedom)

MIT License

Ideal

The most popular license in the JS environment. It allows doing anything with the code: changing, selling, closing, or embedding it into commercial software.

For Client-Side: The developer simply leaves the original authorship notice in the code of their page.
MIT license text

ISC License

Default for npm

The legal equivalent of MIT, but the text is shortened to a single paragraph. The base license generated by the npm init command.

For Client-Side: Absolutely safe for web applications. No restrictions except keeping the copyright.
ISC license text

Apache 2.0

Patent Protection

Allows commercial use and code closure, but additionally protects developers from patent disputes and trolls.

For Client-Side: If the library code is modified directly on the website, it is necessary to indicate which files were changed.
Apache 2.0 license text

BSD (2/3-Clause)

Safe

Allows free use, modification, and sale. The 3-Clause version specifically prohibits using the library author's name for website advertising.

For Client-Side: Full compatibility with any commercial front-end projects.
BSD 2-Clause license text BSD 3-Clause license text

Unlicense / CC0 (Public Domain)

Public Domain

Complete and unconditional waiver of any copyrights worldwide. The code transforms into public use.

For Client-Side: A user of our site has the right to copy a JS function, erase all mentions, and pass the code off as their own. There are no restrictions at all.
Unlicense license text

Safe Copyleft (Weak Mutual Agreement)

MPL 2.0 (Mozilla Public License)

File-level copyleft

The license protects only the library itself, but not the code of the web application that calls it via scripts. Great for isolated JS modules.

For Client-Side: A developer can freely use this JS library on their commercial website. But if they change the code inside the files of the library itself, they must make those modified files publicly available (for example, make a fork on GitHub). The main code of the site remains protected and closed.
MPL 2.0 license text

LGPLv3 (GNU Lesser General Public License)

Dynamic Connection

The license requires that the user can independently replace the version of the library. In a web environment where code is bundled, this creates legal nuances, but it remains safe with the correct architecture.

For Client-Side: You can freely use this library on your commercial website if you connect it as an isolated external module (e.g., via CDN) or interact with its API without static merging (bundling) with the main code of your application. If you do not change the original library code, the copyleft conditions are not activated, and your commercial code remains completely closed.
LGPLv3 license text

Licensing Details (Dual Licensing)

Dual Licensing (e.g., MIT / GPLv3)

Safe when choosing MIT

Some JS libraries (like the popular JSZip) are supplied under two licenses simultaneously. This is done for compatibility with large GPL projects (like WordPress).

For Client-Side: You have the legal right to choose precisely the MIT license. The code of your web application will remain private and closed, and the restrictions of GPLv3 will not affect you.