Context
package.json declares the project as MIT:
but the repository's own LICENSE file is CC0 1.0 Universal, and README.md ("dedicated to the public domain and licensed under Creative Commons Zero") and https://typeset.lllllllllllllllll.com/ say the same. GitHub reports the repository licence as CC0-1.0.
Impact
license is a published manifest field, so the MIT declaration travels further than the repository:
- npm and automated licence-compliance tooling record
typeset as MIT.
package-lock.json inherits the same value for the root package.- The webpack banner is built from this field, so the bundle it emits is stamped with it —
build/typeset.js.LICENSE.txt reads @license MIT.
CC0 and MIT impose different obligations on downstream users, so the two declarations disagree about what consumers may assume.
Solution
Set "license": "CC0-1.0" in package.json and refresh package-lock.json so the root package entry matches. No source changes are needed.
Context
package.jsondeclares the project as MIT:but the repository's own
LICENSEfile is CC0 1.0 Universal, andREADME.md("dedicated to the public domain and licensed under Creative Commons Zero") and https://typeset.lllllllllllllllll.com/ say the same. GitHub reports the repository licence asCC0-1.0.Impact
licenseis a published manifest field, so the MIT declaration travels further than the repository:typesetas MIT.package-lock.jsoninherits the same value for the root package.build/typeset.js.LICENSE.txtreads@license MIT.CC0 and MIT impose different obligations on downstream users, so the two declarations disagree about what consumers may assume.
Solution
Set
"license": "CC0-1.0"inpackage.jsonand refreshpackage-lock.jsonso the root package entry matches. No source changes are needed.