Licenses
Open Source Licenses
NanoStack Lab uses two complementary licenses: MIT (max freedom) and GPLv3 (ensures derivatives stay open).
Module License Overview
| Module | License | Key Characteristic |
|---|---|---|
| CorroSim (corrosion simulation) | MIT | Permissive · Commercial allowed · Keep notice |
| SpecATR (FTIR‑ATR toolkit) | MIT | Permissive · Commercial allowed · Keep notice |
| PolymerBuilder | MIT | Permissive · Commercial allowed · Keep notice |
| AgeCompare | MIT | Permissive · Commercial allowed · Keep notice |
| ThermoNASA (thermal analysis) | GPLv3 | Copyleft · Derivatives must be GPL |
| Java / Python APIs (core libraries) | MIT | Permissive for integration |
All modules are free, open source. GPLv3 modules require derivative works to also use GPLv3. MIT modules can be used in proprietary software.
MIT License
⚡ Permissive · Commercial-friendly
What you can do:
- Use, copy, modify, merge, publish, distribute, sublicense
- Sell copies of the software
- Integrate into proprietary applications (closed source allowed)
Only requirement: Include the original copyright and permission notice.
Warranty: No warranty — “AS IS”.
Read full MIT License →GNU GPL v3
🛡️ Copyleft · Share-alike · Strong open source
What you can do:
- Use, modify, distribute, sell copies
- Patent protection and forbids tivoization
Critical requirement:
- Derivative works must also be GPLv3 (copyleft)
- Source code must be provided
- State significant changes
MIT vs GPLv3 – Which one to choose?
MIT is best when:
- You want maximum adoption
- You want companies to use your code in proprietary products
- You want minimal legal friction
GPLv3 is best when:
- You want to ensure improvements stay open source
- You want to protect against patent lawsuits
- You want a “share-alike” community license