npm / npm/rfcs

[RRFC] move to MIT as default license for `npm init`, away from ISC

Open
#597 6 comments 7 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
777
Forks
267
PR merge metrics
No merged PRs in 30d

Description

Motivation ("The Why")

MIT is - in my experience - the general intentional default in the JavaScript ecosystem. Additionally, Wikipedia notes that the ISC itself has recommended that the MIT license should be preferred over the ISC license, though the reference is currently broken.

How

Replace ISC with MIT in almost all instances here.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked search for isc in the npm/init-package-json codebase and review all matching instances to determine which are defaults used by npm init. Confirm the intended scope from the RFC discussion, then verify that the relevant generated package metadata uses MIT instead of ISC.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
cli
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.