Thanks for publishing this — 68 tools on top of lightweight-charts primitives is a lot of work.
While evaluating it for a commercial product I checked the licensing and found that the license text itself is missing:
package.json declares "license": "MIT" and the README ends with ## License / MIT,- but there is no
LICENSE file in the repository root (GitHub's /license API returns 404 and the repo shows no detected license),
- and the npm tarball for
0.1.1 (7 files) doesn't include one either; the bundles carry no license header.
The MIT license only works if "the above copyright notice and this permission notice" accompany the software, so without the file the grant is ambiguous — and cautious downstream users (or their legal review) can't rely on it.
Would you consider adding a LICENSE file with the standard MIT text and your copyright line, and making sure it ships in the npm package (npm includes LICENSE* files automatically, so just adding it to the repo root is enough)?
Happy to open a PR with the file if you tell me the copyright holder name to put on it.
Thanks for publishing this — 68 tools on top of lightweight-charts primitives is a lot of work.
While evaluating it for a commercial product I checked the licensing and found that the license text itself is missing:
package.jsondeclares"license": "MIT"and the README ends with## License/MIT,LICENSEfile in the repository root (GitHub's/licenseAPI returns 404 and the repo shows no detected license),0.1.1(7 files) doesn't include one either; the bundles carry no license header.The MIT license only works if "the above copyright notice and this permission notice" accompany the software, so without the file the grant is ambiguous — and cautious downstream users (or their legal review) can't rely on it.
Would you consider adding a
LICENSEfile with the standard MIT text and your copyright line, and making sure it ships in the npm package (npm includesLICENSE*files automatically, so just adding it to the repo root is enough)?Happy to open a PR with the file if you tell me the copyright holder name to put on it.