Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Reference to GPL license remains in source file

See original GitHub issue

With #32 my understanding is that the valid license is MIT. However in this file (https://github.com/glejeune/node-graphviz/blob/master/lib/ext/gvpr/dot2js.g) there is still a GPL license referenced. Can that be removed as well?

Issue Analytics

State:
Created 3 years ago
Reactions:4
Comments:5

Top GitHub Comments

2reactions

WernerClemenscommented, Mar 10, 2022

The new package graphviz-mit has a package.json with MIT license, but unfortunately this does not solve the two problems from the beginning of this issue-thread raised by @petergrau and @nemtsov

In this file (https://github.com/glejeune/node-graphviz/blob/master/lib/ext/gvpr/dot2js.g) there is still a GPL license referenced. Can that be removed as well?
The wonderful module madge has as dependency the graphviz (and not the graphviz-mit) and madge can not be used in context where GPL is not allowed. Note, madge and all other dependencies have MIT license.

As @VReichelt said: A new MIT-only release [of graphviz] on npm would be really helpful. Thanks!

2reactions

dubzzzcommented, May 3, 2021

@glejeune Is there a motivation to keep a dependency towards a GPL script?

It seems that keeping this GPL-licensed script bundled into the published package mark the package as GPL. NPM registry flags the package as GPL, see: https://www.npmjs.com/package/graphviz.