License
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 281
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Description
Hi, all the packages published prior to July 22, 2016 have the package LICENSE file as WTFPL (which matches the LICENSE in the repo), while the metadata file (package.json says “BSD").
Question: what is the license for the NPM packages for v0.4.2 and earlier (1) WTFPL license, (2) “BSD” (BSD-3-Clause?) or (3) dual-licensed?
Thanks.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the repository LICENSE with package.json and the published package metadata for v0.4.2 and earlier. The issue is done when a maintainer confirms whether the packages are WTFPL, BSD-3-Clause, or dual-licensed and that answer is recorded in the relevant license metadata or documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100