aboutcode-org / aboutcode-org/scancode-toolkit
Ensure the "licenseref-license" convention of npm before 3.10 is detected correctly
- Langage dominant
- Python
- Étoiles
- 2.6k
- Forks
- 791
- Merge moyen
- 1 j 12 h
- PR mergées (30 j)
- 5
Description
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
Guide de contribution
Ouvrir le guide de contribution
Évaluation
Cette issue n'a pas encore été évaluée.