Skip to content

docs: add MIT license - #25

Open
mdsaif45 wants to merge 1 commit into
mainfrom
add-license
Open

docs: add MIT license#25
mdsaif45 wants to merge 1 commit into
mainfrom
add-license

Conversation

@mdsaif45

Copy link
Copy Markdown
Owner

Why

The repo presented as open source — the README has a License & Governance section and the landing page footer says "open source under the project's licence" — but no license was ever declared. Without a LICENSE file the code is legally all-rights-reserved, so nobody could reuse or fork it.

GitHub also reported license: null on the repo, and the open-source topic had nothing backing it.

Changes

File Change
LICENSE MIT, verbatim canonical text, © 2026 MD SAIF
package.json Added "license": "MIT"
README.md Named the license under the existing heading

Notes

  • License text was diffed against GitHub's canonical MIT template (gh api licenses/mit) and is a word-for-word match, so GitHub's license detector will pick it up and show an MIT badge.
  • Copyright holder taken from the git history / GitHub profile name (MD SAIF).
  • MIT chosen as the permissive default that matches the "yours to fork" framing. Happy to switch to Apache-2.0 (adds a patent grant) or AGPL-3.0 (copyleft, requires sharing changes to hosted versions) if you'd prefer — it's a one-file swap.
  • No source code touched; docs/ is untouched and stays on gh-pages.

The README had a 'License & Governance' section that never named a
license, and package.json had no license field, so the project was
technically all-rights-reserved despite presenting as open source.

- LICENSE: MIT, verbatim canonical text, (c) 2026 MD SAIF
- package.json: declare "license": "MIT"
- README: state the license under the existing heading
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.

1 participant