Add ISC License to Repository

[10xLaCroixDrinker]

This repository is currently unlicensed, which can limit its adoption and use in corporate environments. To address this, I'm adding the ISC License, which is widely used other npm projects. This will clarify the terms of use and make the repository more accessible to contributors and users.

By adding the ISC License, we can ensure clarity and consistency across npm projects, and make this repository more open and inclusive for everyone.

Validated with licensee gem:

$ docker run -v "$HOME/git/registry:/registry" licensee detect /registry
License:        ISC
Matched files:  LICENSE.md
LICENSE.md:
  Content hash:  7fcb74e2084b361556b8285d6f800495d0d5e36a
  Attribution:   Copyright npm, Inc.
  Confidence:    100.00%
  Matcher:       Licensee::Matchers::Exact
  License:       ISC

[Maniues]

@10xLaCroixDrinker Great idea! Some npm docs are licensed under CC-BY, so maybe CC-BY or dual-licensing under ISC/CC-BY is more appropriate.
Maybe it's worth asking and mentioning people from npm
@MylesBorins @darcyclarke what do you think about this?

[leobalter]

Thank you for your contribution and for proposing the ISC license for this project. After careful consideration, we have decided not to proceed with changing the project's license at this time. We appreciate your understanding and continued support of the project.

[Maniues]

@leobalter npm is one of the most important programs for Node.js. The npm registry is one of the key elements of this environment. What really amazes me is the fact that not only is the registry closed source (which I can still understand), but the API documentation of this registry is not made available for free use by the community. I am asking you to consider making this documentation available under an Open Source license, whether ISC, CC-BY or any other, because it is an Open Source element and since the documentation is already available, there is really no problem in making it available under such conditions.
Attempts to force this documentation to be separate and closed may only encourage people to create forks, reimplement and defragment the environment, which is probably not beneficial for either the community or npm.

[Dropkick13]

Okay thank u so much with getting back to me with the information and I will see about fixing that

…

On Fri, May 24, 2024, 11:44 AM Maniues ***@***.***> wrote: @leobalter <https://github.com/leobalter> npm is one of the most important programs for Node.js. The npm registry is one of the key elements of this environment. What really amazes me is the fact that not only is the registry closed source (which I can still understand), but the API documentation of this registry is not made available for free use by the community. I am asking you to consider making this documentation available under an Open Source license, whether ISC, CC-BY or any other, because it is an Open Source element and since the documentation is already available, there is really no problem in making it available under such conditions. Attempts to force this documentation to be separate and closed may only encourage people to create forks, reimplement and defragment the environment, which is probably not beneficial for either the community or npm. — Reply to this email directly, view it on GitHub <#30 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BHMV6BC3IX3K36LIHML4FP3ZD5U7ZAVCNFSM6AAAAABG2PL27SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRZHE3TKMZYG4> . You are receiving this because you commented.Message ID: ***@***.***>