argparse@2 (used with nx) with GPL license: does it force everyone that uses nx to make their software open source?

[rkristelijn]

Context: I'm new to licence management but found something weird in the dependency tree, specifically argparse@2 with GPL license, while argparse@1 has MIT license. nx has MIT license.

I discoved this by running npx nlf

❯ npm ls argparse@2
├─┬ @nx-extend/[email protected]
│ └─┬ @strapi/[email protected]
│   └─┬ [email protected]
│     └── [email protected]
├─┬ @nx/[email protected]
│ └─┬ [email protected]
│   └── [email protected]
└─┬ [email protected]
  └─┬ @zkochan/[email protected]
    └── [email protected]

Assumption: the thing is that GPL is copyleft so nx can be claimed as opening his source code. It is already open source, so that is no issue. But is everyone else that uses nx too?

Other question, can we opt-out for use of argparse@2?

[rkristelijn]

Digging further, it has been discussed by js-yaml nodeca/js-yaml#667 referencing https://en.wikipedia.org/wiki/Python_Software_Foundation_License

https://www.npmjs.com/package/argparse @2.0.1 currently has Python-2.0 licence

https://github.com/nodeca/argparse/blob/master/package.json#L17C15-L17C25 says Python-2.0 :

It is not Copyleft, so I think no worries here. You may close the question if you agree.