aboutcode-org / aboutcode-org/scancode-toolkit

Ensure the "licenseref-license" convention of npm before 3.10 is detected correctly

未关闭
#2,872 6 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
easy good first issue license scan package scan
主要语言
Python
星标
2.6k
派生
791
平均合并
1 天 12 小时
30 天内合并 PR
5

描述

See https://github.com/search?p=2&q="LicenseRef-LICENSE"&type=Code

Over the years, npm had a few evolving conventions:

See https://softwareengineering.stackexchange.com/questions/285885/which-spdx-license-is-equivalent-to-all-rights-reserved

https://github.com/npm/npm/issues/8795#issuecomment-119760485

> Use "license": "LicenseRef-LICENSE" and then create a LICENSE file next to package.json with something as little as: "(c) Copyright 2015 person or company, all rights reserved.".

and https://www.bonbon.io/commercial-licenses-for-npm-packages
> This should be enough to satisfy NPM commands if you had a missing or incorrect license, and this does replace the older "license": "LicenseRef-LICENSE" of earlier NPM versions.

This legacy way should be supported. It is seen on bower packages too

贡献指南

打开贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。