Earlier this week, many npm users suffered a disruption when a package
that many projects depend on — directly or indirectly — was
unpublished by its author, as part of a dispute over a package name.
The event generated a lot of attention and raised many concerns,
because of the scale of disruption, the circumstances that led to this
dispute, and the actions npm, Inc. took in...