From: Mike Gerwitz <mtg@gnu.org>
To: Jelle Licht <jlicht@fsfe.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: npm (mitigation)
Date: Fri, 14 Jul 2017 23:34:51 -0400 [thread overview]
Message-ID: <871spi5q5g.fsf@gnu.org> (raw)
In-Reply-To: <CAPsKtfKrcMa0RdB3EYJ6R8iUh7boKbH_59FUwtmspjBT_tUvaw@mail.gmail.com> (Jelle Licht's message of "Fri, 14 Jul 2017 13:57:30 +0200")
[-- Attachment #1: Type: text/plain, Size: 825 bytes --]
On Fri, Jul 14, 2017 at 13:57:30 +0200, Jelle Licht wrote:
> Regardless, the biggest issue that remains is still that npm-land is mired
> in cyclical dependencies and a fun-but-not-actually unique dependency
> resolving scheme.
I still think the largest issue is trying to determine if a given
package and its entire [cyclic cluster] subgraph is Free. That's a lot
of manual verification to be had (to verify any automated
checks). npm's package.json does include a `license' field, but that is
metadata with no legal significance, and afaik _defaults_ to "MIT"
(implying Expat), even if there's actually no license information in the
repository.
--
Mike Gerwitz
Free Software Hacker+Activist | GNU Maintainer & Volunteer
GPG: D6E9 B930 028A 6C38 F43B 2388 FEF6 3574 5E6F 6D05
https://mikegerwitz.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2017-07-15 3:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-14 8:52 npm (mitigation) Catonano
2017-07-14 11:57 ` Jelle Licht
2017-07-15 3:34 ` Mike Gerwitz [this message]
2017-07-15 3:57 ` Jelle Licht
2017-07-15 17:39 ` Adonay Felipe Nogueira
2017-07-15 16:51 ` Adonay Felipe Nogueira
2017-07-17 9:45 ` Catonano
2017-07-18 2:12 ` Mike Gerwitz
2017-07-17 9:28 ` Catonano
2017-07-24 15:39 ` Ricardo Wurmus
2017-07-25 6:37 ` Catonano
2017-07-14 17:11 ` Jan Nieuwenhuizen
2017-07-17 9:32 ` Catonano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871spi5q5g.fsf@gnu.org \
--to=mtg@gnu.org \
--cc=guix-devel@gnu.org \
--cc=jlicht@fsfe.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).