# Sonatype doesn't get npm package license from package repo

**URL:** <https://community.sonatype.com/t/sonatype-doesnt-get-npm-package-license-from-package-repo/12850>\
**Category:** Sonatype Lifecycle & Firewall\
**Tags:** license, npm\
**Created:** [July 3, 2024, 9:44am UTC](https://community.sonatype.com/t/sonatype-doesnt-get-npm-package-license-from-package-repo/12850 "2024-07-03T09:44:48Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![pri](https://yyz1.discourse-cdn.com/flex047/user_avatar/community.sonatype.com/pri/32/3527_2.png) [@pri](https://community.sonatype.com/u/pri)\
**Post date:** [July 3, 2024, 9:44am UTC](https://community.sonatype.com/t/sonatype-doesnt-get-npm-package-license-from-package-repo/12850/1 "2024-07-03T09:44:49Z")

</div>

Is there a way to inform Sonatype about npm package licenses if they are not included within the package?

We’re using [redoc](https://www.npmjs.com/package/redoc) to generate API reference documentation. Among the packages that redoc depends on, there are a few with no license information within the package, while they are, in fact, licensed; each of these packages links to a GitHub repository with a LICENSE file (MIT).

---

_[View the full topic](https://community.sonatype.com/t/sonatype-doesnt-get-npm-package-license-from-package-repo/12850)._