README.md links to [LICENSE](LICENSE) but no LICENSE file exists in the repository, so that link 404s and GitHub reports no license for the project (licenseInfo: null via the API, and no license shown in the repository sidebar).
Location
README.md — "This project is licensed under the MIT License - see the LICENSE file for details."
- Repository root — no
LICENSE or LICENSE.md file
package.json — no license field
Why this matters
Without a license file, the default position under copyright is that no one has permission to use, modify, or distribute the code, regardless of what the README asserts. GitHub's own guidance is that a repository without a license grants no rights beyond viewing and forking within the platform's terms.
This matters now specifically because the project is being opened to outside contributors. A contributor has no clear basis on which they are contributing, and anyone wanting to reuse the code has no grant to rely on. The README already states the intent is MIT, so this is a matter of making the stated intent actually effective rather than a licensing decision.
Suggested fix
- Add a
LICENSE file at the repository root containing the standard MIT License text, with the correct copyright year and holder.
- Add
"license": "MIT" to package.json so tooling and the npm ecosystem can read it.
- Confirm afterwards that GitHub displays "MIT" in the repository sidebar — that is the signal that the file was recognised, since a malformed or renamed file is silently ignored.
Worth deciding explicitly who the copyright holder is (the original author, or the author plus contributors) before writing the file.
README.mdlinks to[LICENSE](LICENSE)but noLICENSEfile exists in the repository, so that link 404s and GitHub reports no license for the project (licenseInfo: nullvia the API, and no license shown in the repository sidebar).Location
README.md— "This project is licensed under the MIT License - see the LICENSE file for details."LICENSEorLICENSE.mdfilepackage.json— nolicensefieldWhy this matters
Without a license file, the default position under copyright is that no one has permission to use, modify, or distribute the code, regardless of what the README asserts. GitHub's own guidance is that a repository without a license grants no rights beyond viewing and forking within the platform's terms.
This matters now specifically because the project is being opened to outside contributors. A contributor has no clear basis on which they are contributing, and anyone wanting to reuse the code has no grant to rely on. The README already states the intent is MIT, so this is a matter of making the stated intent actually effective rather than a licensing decision.
Suggested fix
LICENSEfile at the repository root containing the standard MIT License text, with the correct copyright year and holder."license": "MIT"topackage.jsonso tooling and the npm ecosystem can read it.Worth deciding explicitly who the copyright holder is (the original author, or the author plus contributors) before writing the file.