MetaMask / MetaMask/metamask-extension
Setup API leakage monitoring
Open
area-api
area-privacy
team-extension-platform
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
## Background
We don't have an automated way to determine API calls to third parties could potentially leak sensitive private data. We should set up an automated way to perform quality checks on data privacy using Circle CI.
Reference: https://www.notion.so/API-services-72fb28c76c1e4e08b09bfa399b844296#a91b1a1b811242b7bac78724005af7df
## User Story
TBD
Contributor guide
Research direction
The issue names no repository files, tests, or entry points. Start by reviewing the Circle CI configuration and the linked API-services reference to define the checks and their scope. Done means an automated quality check can identify third-party API calls that may expose sensitive private data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- ci-cd, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100