MPL-2.0 Licence not aligned with the rest of Next.js / Vercel that uses MIT and triggers legal queries

Open
#166 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
analytics

Research direction

Start by reviewing the Analytics package's current MPL-2.0 licensing and the linked Next.js discussion about aligning packages with MIT. Confirm with maintainers and legal stakeholders whether the package can change licenses; done means the decision is documented and the repository's licensing metadata reflects the approved outcome.

Written by the indexing model from the issue text.

Description

Hi There,

Similar to the issue below for the Edge Runtime and Next.js, using the MPL-2.0 licence triggers lots of queries from legal departments when used.

https://github.com/vercel/next.js/issues/38467#issuecomment-2214509969

Is there any reason the Analytics package that must be installed to get full Vercel Analytics Capability is MP-2.0 rather then MIT like the rest of next.js etc?

Could this change as Vercel has done with the edge runtime packages in the comment above to align on the MIT license?

Many Thanks in advance!,
Jon

Dominant language
TypeScript
Stars
515
Forks
52
Avg merge
1h 16m
Merged PRs (30d)
2

Contributor guide

No contributing guide indexed for this repository

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.

More from vercel/analytics

All issues in vercel/analytics

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.