Hi,

It looks like the published @microsoft/clarity npm package does not include the LICENSE file, even though the repository contains it.

The package correctly specifies its license in package.json, but many OSS compliance tools rely on the published package containing the full license text (e.g. a LICENSE, LICENSE.txt, or similar file). Without it, these tools report a missing license text and require consumers to implement custom workarounds.

Would it be possible to include the LICENSE file in future npm releases?

This would improve compatibility with license scanning and compliance tools while remaining consistent with how most npm packages are published.

Thanks!