Licensing Guide — Provider-Aware Statusline¶
This repository uses a dual-license model to clearly separate code (executable components) from documentation and knowledge artifacts.
| Component | License | Notes |
|---|---|---|
| Code / Executables / Config | MIT | Statusline/**, Scripts/**, .claude/settings.json, .claude/settings.local.example.json, .gitignore, package.json |
| Documentation / Knowledge / Media | CC BY 4.0 | All *.md files, Research/**, Findings/**, References/**, Statusline/Design/**, Assets/** |
Inbound Contributions¶
- Code contributions are licensed to the repository under MIT (the license of the repository's code components).
- Documentation contributions are licensed to the repository under CC BY 4.0 (the license of the repository's documentation components).
This dual model ensures that: - Users can freely install, modify, and redistribute the tool under MIT. - Readers can freely share and adapt the engineering knowledge under CC BY 4.0. - There is no ambiguity about which license applies to which part of the repository.
License File Locations¶
LICENSE— MIT full text (code components).LICENSE.docs— CC BY 4.0 full text (documentation components).LICENSING.md— this guide.
SPDX Headers¶
Every source file in the code category carries the SPDX identifier:
// SPDX-License-Identifier: MIT
No SPDX header is used in documentation files; they are governed by LICENSE.docs (CC BY 4.0).
GitHub Repository License¶
The GitHub repository's "License" field is set to MIT to reflect the code-first nature of the project.
Questions?¶
See CONTRIBUTING.md for contribution guidelines and inbound-license expectations.