Skip to content

docs: add scoped MIT license and fork provenance audit - #180

Merged
mstrhakr merged 2 commits into
devfrom
licensing/mit-contributions
Oct 12, 2026
Merged

mstrhakr merged 2 commits into
devfrom
licensing/mit-contributions

Conversation

@mstrhakr

Copy link
Copy Markdown
Owner

This pull request introduces a comprehensive update to the project's licensing documentation to clarify the scope and limitations of the MIT license for this fork. It adds detailed explanations about which parts of the codebase are covered, the status of inherited and third-party material, and the steps required before the project can be considered fully open source. The changes aim to increase transparency and legal clarity for contributors and users.

Licensing scope clarification:

  • Added a detailed license scope notice to both the main LICENSE file and source/compose.manager/licenses/PROJECT-LICENSE.txt, specifying that the MIT license applies only to original material by Nick Szittai (mstrhakr), and does not cover inherited upstream code, independently owned contributions, or third-party assets. It also states that the repository is not cleared for unrestricted redistribution until upstream permissions are resolved.

  • Updated the README.md to reflect the new licensing scope, explicitly stating that only original material is MIT-licensed, inherited code is excluded, and that the project is not yet cleared for unrestricted redistribution. References to detailed licensing and provenance audit documents were added.

Provenance and audit documentation:

  • Added a new source/compose.manager/licenses/LICENSING.md file containing a thorough audit of the codebase's provenance, including line attribution statistics, upstream code analysis, third-party component review, and a checklist of steps required to resolve outstanding licensing issues.

Copilot AI balanced review requested due to automatic review settings October 12, 2026 13:06

This comment was marked as resolved.

Co-authored-by: mstrhakr <37352843+mstrhakr@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants