Summary
README.md states the project is licensed under MIT, but no LICENSE file exists in the repo. gh repo view confirms licenseInfo: null.
Motivation
Without a LICENSE file, GitHub cannot detect the license, and the MIT claim in the README isn't actually backed by a real license grant. This matters for anyone deciding whether they can legally use, fork, or contribute to the project.
Proposed Solution
Add a standard MIT LICENSE file at the repo root, with the copyright holder and year filled in correctly.
Scope
| Field |
Value |
| Area |
Docs |
| Protocol affected |
None |
| Network |
N/A |
| Breaking change? |
No |
Acceptance Criteria
Summary
README.mdstates the project is licensed under MIT, but noLICENSEfile exists in the repo.gh repo viewconfirmslicenseInfo: null.Motivation
Without a
LICENSEfile, GitHub cannot detect the license, and the MIT claim in the README isn't actually backed by a real license grant. This matters for anyone deciding whether they can legally use, fork, or contribute to the project.Proposed Solution
Add a standard MIT
LICENSEfile at the repo root, with the copyright holder and year filled in correctly.Scope
Acceptance Criteria
LICENSEfile added at the repo root with standard MIT textgh repo viewreports the correctlicenseInfoafter merge