I am wondering if deploying micro-services based on BunJS do require to “provide your application in an object” as stated in the portion of the Webkit licence (included in BunJS it-self):
Sources: https://github.com/oven-sh/bun?tab=License-1-ov-file#readme
Bun statically links JavaScriptCore (and WebKit) which is LGPL-2 licensed. WebCore files from WebKit are also licensed under LGPL2. Per LGPL2: (1) If you statically link against an LGPL’d library, you must also provide your application in an object (not necessarily source) format, so that a user has the opportunity to modify the library and relink the application. You can find the patched version of WebKit used by Bun here….
BunJS it-self is licensed under MIT, that’s why is not clear to me if I have any obligations regarding to Webkit.
If you re-distribute BunJS, with or without changes, then you must provide the recipients of your distribution with the means to replace the JavaScriptCore and Webkit portions of BunJS. That can be achieved by using an open-source license and making the sources available, or if your changes are under a proprietary license, by providing object files that can be re-linked with the modified JavaScriptCore and/or Webkit versions.
On the other hand, if you just use bun as your server-side JavaScript runtime engine, then the licenses of BunJS, JavaScriptCore and Webkit impose no obligations on you.