You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can you publish a new version to NPM which has the proper license tag in package.json (This is already included in master, but the version is not published yet).
Having proper license metadata helps managing large projects with complex dependencies. Currently, when using, e.g., https://github.com/iandotkelly/nlf, this package shows up as a false positive, since the license cannot be automatically detected.
The text was updated successfully, but these errors were encountered:
The newest version of this package on NPM still specifies "license: none" (https://www.npmjs.com/package/component-bind).
Can you publish a new version to NPM which has the proper license tag in package.json (This is already included in master, but the version is not published yet).
Having proper license metadata helps managing large projects with complex dependencies. Currently, when using, e.g., https://github.com/iandotkelly/nlf, this package shows up as a false positive, since the license cannot be automatically detected.
The text was updated successfully, but these errors were encountered: