Plugin license metadata
The license field describes the plugin’s first-party code. It records existing
terms; adding metadata does not relicense any plugin. Dependency, executable,
model and dataset terms remain separate. Read the project’s notices before
redistributing a combined package.
Initial values were checked against the maintained collection’s licensing scope and the license documents at each external entry’s registered release tag. Retired/hidden entries were left unchanged. Existing plugin source files did not receive new license constants.
Most maintained collection plugins use LGPL-3.0-or-later. Exceptions and scope
details include:
| Plugin | Recorded license | Additional context |
|---|---|---|
| OpenBabel Conversion Tool | GPL-2.0-or-later |
External package from v2026.11.02; see its licensing and process-boundary notes. Open Babel retains GPL-2.0-only. |
| Open Babel Optimizer | GPL-2.0-or-later |
Applies from v1.0.1; see its licensing and process-boundary notes. Historical releases retain their original grants. |
| PySCF Calculator | GPL-3.0-only |
Its v5.0.0 licensing notes also grant a geomeTRIC combination permission. The base-license field does not replace that permission or geomeTRIC’s terms. |
| NMR Predictor nmrshiftdb2 | GPL-3.0-only |
The v3.0.0 README distinguishes plugin code from predictor JARs and data. |
| Molibrary Browser | LGPL-3.0-or-later |
The plugin licensing document applies; the web application has a separate root license. |
When a project only grants GPLv3 without an explicit later-version option, the
field uses GPL-3.0-only; it does not infer additional permissions from examples
in the standard license text. Unconfirmed values use NOASSERTION, displayed as
Not specified. Metadata is informational; the actual license documents govern.
For synchronization and reviewed registry-only changes, see CONTRIBUTING.md.