microsoft / microsoft/vscode-pull-request-github
plugin should switch to least privelege permissions
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.6k
- Forks
- 796
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 46
Description
Thanks for this wonderful plugin!
However, I'm hesistant on authorizing this plugin to do EVERYTHING on my Github account.
The plugin requests Github authorization for write (and read) on EVERYTHING - including repo, team discussions, wiki, etc.
Could we switch to using least privilege permissions, where the default set of permissions is scoped down to what's required and the plugin gracefully degrades features based on permissions it is granted?
- Extension version: 0.13.0
Contributor guide
No contributing guide indexed for this repository
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 locating the extension's GitHub authorization scopes and the entry points for features that require them. Review how permissions are currently requested and checked; done means the default authorization is least-privilege and unsupported features gracefully degrade when permissions are missing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, typescript, vscode
- Domain
- authorization, developer-experience, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100