MetaMask / MetaMask/metamask-extension
Add license lint check
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
### What is this about?
We want all of our dependencies to have licenses that are compatible with how we are using them, and compatible with the terms of our license.
We should add a lint check to ensure new packages meet these criteria. For existing packages with licences that don't meet these criteria, we can exclude them from this status check for now and document them as bugs to address separately.
### Scenario
_No response_
### Design
_No response_
### Technical Details
[
Apply same solution to mobile ](https://github.com/MetaMask/metamask-mobile/issues/12204)
### Threat Modeling Framework
_No response_
### Acceptance Criteria
_No response_
### Stakeholder review needed before the work gets merged
- [x] Engineering (needed in most cases)
- [ ] Design
- [ ] Product
- [ ] QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
- [ ] Security
- [x] Legal
- [ ] Marketing
- [ ] Management (please specify)
- [ ] Other (please specify)
### References
_No response_
Contributor guide
Research direction
Start by reviewing the dependency and status-check configuration in this repository, then compare the requested approach with the linked MetaMask Mobile issue 12204. Done means new packages are checked for license compatibility, existing incompatible packages can be excluded temporarily, and those exceptions are documented as bugs for follow-up.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100