Check npm dependencies' package.json for license compatibility (aka compliance check) with the current project based on spdx notation and naming conventions.
License: MIT License
I want to know the source of dev/spdxLicenseData.json. I checked https://spdx.org/licenses/, but couldn't find it.
Can you provide some help? It would be greatly appreciated.
Currently the compatibility checker exit non-zero also on "possible incompatible".
I would like to have a parameter to the checker script to return non-zero (error) only if there is a definitely comparability issue ("y").
Then I could use this package in my CI/CD pipeline.
Regards,
Melroy van den Berg
Hello HansHammel,
Can you add these AGPL variants?
AGPL-3.0-only
AGPL-3.0-or-later
AGPL-1.0-only
AGPL-1.0-or-later
Source: https://spdx.org/licenses/
Thanks for the nice project you have!
Hi,
I'm using license-compatibility-checker as module. When I execute the code I see this error message:
{ [Error: ENOENT: no such file or directory, access '/home/hf/Desktop/license-reporter/node_modules/@babel/package.json']
errno: -2,
code: 'ENOENT',
syscall: 'access',
path:
'/home/hf/Desktop/license-reporter/node_modules/@babel/package.json' }Any chance to suppress this kind of error?
thanks
Hi HansHammel
Is it possible that you can provide some insights on the process you used to determine whether two licenses are incompatible as seen on the charts in the readme? It will be very much appreciated.
The Eclipse Foundation announced version 2.0 on 24 August 2017.
This license is a bit complicated because the initial committer can opt in to GPLv2+ (version 2 or any later version) as part of this license. The wikipedia page mentioned above contains more details and links to primary references.
cheers, Robbie
🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨
To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.
Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet.
We recommend using:
If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.
Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.
🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨
To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.
Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet.
We recommend using:
If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.
Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.
After installing on macOS I'm unable to run the cli ($ license-compatibility-checker) because of the error:
env: node\r: No such file or directory
It seems you have uploaded the files CRLF line endings instead of LF.
Could you possibly switch to LF? (e.g. via .gitattributes or .editorconfig)
Thanks for all of the hard work on this package!
What would you think about combining the functionality in this package with the work being done in tldrlegal? It seems like it would be handy to combine the compatibility checking with the other obligation checking in tldrlegal.
modules org-scoped by name now appear as ./node_modules/@org/package
errors below
{ [Error: ENOENT: no such file or directory, access '/home/xyz/Development/metamask-extension2/node_modules/@types/package.json']
errno: -2,
code: 'ENOENT',
syscall: 'access',
path:
'/home/xyz/Development/metamask-extension2/node_modules/@types/package.json' }
{ [Error: ENOENT: no such file or directory, access '/home/xyz/Development/metamask-extension2/node_modules/@wry/package.json']
errno: -2,
code: 'ENOENT',
syscall: 'access',
path:
'/home/xyz/Development/metamask-extension2/node_modules/@wry/package.json' }
{ [Error: ENOENT: no such file or directory, access '/home/xyz/Development/metamask-extension2/node_modules/@xtuc/package.json']
errno: -2,
code: 'ENOENT',
syscall: 'access',
path:
'/home/xyz/Development/metamask-extension2/node_modules/@xtuc/package.json' }
{ [Error: ENOENT: no such file or directory, access '/home/xyz/Development/metamask-extension2/node_modules/@webassemblyjs/package.json']
errno: -2,
code: 'ENOENT',
syscall: 'access',
path:
'/home/xyz/Development/metamask-extension2/node_modules/@webassemblyjs/package.json' }
{ [Error: ENOENT: no such file or directory, access '/home/xyz/Development/metamask-extension2/node_modules/@zxing/package.json']
errno: -2,
code: 'ENOENT',
syscall: 'access',
path:
'/home/xyz/Development/metamask-extension2/node_modules/@zxing/package.json' }
🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨
To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.
Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet.
We recommend using:
If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.
Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.
I would like to use license-compatiblity-checker in a CI pipeline/workfow.
It should only fail if a new package with an incompatible license has been added.
Currently I get errors like
[email protected] (MIT OR CC0-1.0) (Unknown) - possibly incompatible with AGPL-3.0 (Network Protective)
[email protected] No license (Unlicensed) - possibly incompatible with AGPL-3.0 (Network Protective)
=> How can I manually allow some of the (unknown) licenses / add them to a whitelist?
its common to have this file in the root of the directory
eg https://github.com/MetaMask/metamask-extension/blob/f5b2977764f13df0f0b478718383415156c67a7b/LICENSE
0BSD is defined here: https://opensource.org/licenses/0BSD
It's a derivative of the ISC License. The program flags this license as unknown and possibly incompatible.
yarn license-compatibility-checker emits
env: node\r: No such file or directory
error Command failed with exit code 127.
while npx license-compatibility-checker successfully runs.
🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨
To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.
Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet.
We recommend using:
If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.
Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.