npm Community Forum (Archive)

The npm community forum has been discontinued.

To discuss usage of npm, visit the GitHub Support Community.

Question regarding license field value in package.json


I work with a team which is in the process of creating custom npm packages which gets published to our organization’s on-premise Artifactory instance. These custom npm packages will be used by other teams in our organisation and outside. The custom npm packages are built using multiple dependencies including @stencil/core, chai, typescript etc. Under circumstances where other teams will be using our custom packages in their projects, what should the license field value in the package.json be ? Can it be Unlicensed like how we currently have it ? Or should the license type be more permissive when compared to the licenses of the dependencies used by our npm package ? Or can we just have our organization’s name as the license field value ? Please note that these custom npm packages being built by us is only published to an on-prem Artifactory instance and not anywhere else.

Thanks much.