NOTICE.md

Licenses Used In MetaCall (Optional)

All external code and licenses used by METACALL are always wrapped into plugins and linked dynamically to them. By this reason the METACALL core is not polluted with licenses or software restrictions. The developer can choose what plugins wants to use in order to fit their requirements. All license requirements are optional.

Table Of Contents

• Licenses Used In MetaCall (Optional)
• Table Of Contents
  • 1. Loaders
    • 1.1 Python
    • 1.2 NodeJS
    • 1.3 JavaScript (V8)
    • 1.4 C#
    • 1.5 Ruby
    • 1.6 C/C++
    • 1.6 JavaScript (SpiderMonkey)
  • 2. Serials
    • 2.1 RapidJSON
  • 3. Detours
    • 3.1 FuncHook
  • 4. Ports
    • 4.1 Swig

1. Loaders

1.1 Python

Software	License
Python	Python Software Foundation License

1.2 NodeJS

Software	License
NodeJS	MIT License

1.3 JavaScript (V8)

Software	License
V8	BSD 3-clause License

1.4 C#

Software	License
NetCore	MIT License License

1.5 Ruby

Software	License
Ruby	BSD 2-clause License - Ruby License

1.6 C/C++

Software	License
Clang - LLVM	University of Illinois/NCSA Open Source License
LibFFI	MIT License

1.6 JavaScript (SpiderMonkey)

Software	License
SpiderMonkey	Mozilla Public License 2.0

2. Serials

2.1 RapidJSON

Software	License
RapidJSON	MIT License

3. Detours

3.1 FuncHook

Software	License
FuncHook	GPLv2 or later with a GPL linking exception

4. Ports

4.1 Swig

Software	License
SWIG	∅

When SWIG is used as it is distributed by the SWIG developers, its output is not governed by SWIG's license (including the GPL). SWIG's output contains code from three sources:

• code generated by SWIG, which is not governed by copyright;
• code copied from the SWIG library which is permissively licensed to be redistributed without restriction;
• code derived from the user's input, which may be governed by the license of the code supplied by the user.

So, while the input supplied to SWIG may affect the license of SWIG's output (e.g. if the input code is licensed under a copyleft or proprietary license), SWIG's license does not affect the license of the output. This is consistent with the FSF's FAQ entries on this subject (GPLOutput and WhatCaseIsOutputGPL), because the SWIG code copied into the output by SWIG is not GPL-licensed.