Bug: Treatment of UNLICENSED when package not private about license-checker HOT 3 OPEN

@Undistraction May I ask why you're running license checker?

from license-checker.

We have very similar situation and problem. We have several apps that use our internal npm packages from our internal npm registry. Our packages are not set private in package.json. The packages are for internal projects only, so they are not licensed. Therefore we have "license": "UNLICENSED", in package.json.

We use license-checker to list all packages we use and their licenses, to give our users the access to that information if they are to need it. This could be for legal, or what ever purpose. ATM the license-checker fallbacks to our readmes which can result to a security issue if someone mistakenly puts some delicate information there. Anyway, we don't want to show our readmes in the apps in the license page. They don't make any sense in the license list context.

We would very much appreciate the support to also list license info for unlicensed not private packages.

PS. This is a great library. Thank you for making it! 🙏

from license-checker.

If the project is under a MIT license (https://github.com/ngx-translate/core/blob/master/LICENSE), why isn't it in the package.json? It could make things easier to the license-checker

from license-checker.