Quoting Philippe Ombredanne (2022-05-02 13:43:56)
On Mon, May 2, 2022 at 10:46 AM Till Jaeger via lists.spdx.org
I noticed that NPM is using an Artistic-2.0 with additional terms This is IMHO a total and complete mess and non-sense, eventually non
FOSS at all.
Anyone from Microsoft or GitHub to fix this monstrosity?
Release notes for npm v2.14.13 contains the following:
npm-the-CLI is licensed under the terms of the [Artistic License
which is a liberal open-source license that allows you to take this
code and do pretty much whatever you like with it (that is, of course,
not legal language, and if you're doing anything with npm that leaves
you in doubt about your legal rights, please seek the review of
qualified counsel, which is to say, not members of the CLI team, none
of whom have passed the bar, to my knowledge). At the same time the
primary registry the CLI uses when looking up and downloading packages
is a commercial service run by npm, Inc., and it has its own [Terms of
So seems to me (assuming licensing hasn't changed since v2.14.13) the
command-line tool *is* freely licensed, and only when describing
npm-as-a-whole-including-online-service is it not free.
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private