Licensing at NNN

Philosophy

No Nut November supports open collaboration while recognizing practical constraints: some code must remain closed to protect security, reduce abuse vectors, or uphold legal and partner obligations. We employ a mixed‑open model: open, partially open, and closed components.

Open components

These components are available under OSI‑approved licenses, enabling use, modification, and distribution under the terms of their licenses. Examples: UI libraries, SDKs, non‑sensitive tooling.

• Permissive: MIT, BSD‑3‑Clause, Apache‑2.0
• Copyleft: GPL‑3.0, AGPL‑3.0 (case‑by‑case)

Partially open components

Source is available with additional restrictions to protect ecosystem safety, brand integrity, or prevent misuse. Example approaches include:

• Source‑available licenses with usage limits (e.g., BSL‑1.1, SSPL, Elastic License) when appropriate.
• Dual‑licensing: open for community/non‑commercial, commercial license for production or revenue use.
• Delayed‑open model: initially closed, scheduled to relicense to a permissive license after a stabilization period.

Closed components

Security‑sensitive or abuse‑prone logic may remain proprietary. We aim to minimize closed code while maintaining user safety and platform reliability. Closed code remains subject to No Nut November proprietary rights.

Attribution and trademarks

Use of No Nut November trademarks, logos, and brand assets is governed by our brand guidelines and is not granted by default through software licenses. Respect upstream license attribution requirements where applicable.

Patent policy: Unless expressly granted in a license, no patent rights are conveyed. For Apache‑2.0 components, a patent license is granted under the terms of that license.

Contributions

Contributions to open or source‑available repositories are welcome. By submitting a contribution, you agree it will be licensed under the project’s stated license and that you have the right to submit it. We may use a Contributor License Agreement (CLA) for clarity.

Third‑party compliance: Some components include third‑party code; you must comply with their respective licenses.

License selection guidelines

• Libraries/tooling intended for broad adoption: MIT or Apache‑2.0.
• Networked services where improvements should flow back: AGPL‑3.0 or SSPL (case‑by‑case, with clear notice).
• Security‑sensitive modules or anti‑abuse logic: closed or source‑available with safeguards (e.g., BSL‑1.1).
• Apps with mixed value: dual‑license or delayed‑open.

Commercial licensing: For use cases not permitted by a public license (e.g., certain hosted, OEM, or revenue use), contact us to discuss commercial terms.

FAQ

• Can I use No Nut November open components in commercial apps? Yes, subject to their specific license terms.
• Can I self‑host? For permissive and AGPL components, yes; for source‑available, see the license terms.
• Will more code open over time? Our intent is to open as much as is safe and sustainable.

Contact

Licensing questions? Contact us at privacy@nonutnov.fun.