mazzzystar / mazzzystar/tinymind
[Suggestion] Limit GitHub authorization scope to selected repositories instead of all public repos
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 807
- Forks
- 61
- PR merge metrics
- No merged PRs in 30d
Description
First of all, Tinymind is a fantastic tool.
I've noticed an area where I believe we could enhance user privacy and security: When logging in with GitHub, users need to authorize Tinymind to access all of their public GitHub repositories, which seems unnecessary. Could we limit the access to selected repositories instead?
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 tracing the GitHub login and authorization flow; the issue does not name a file, test, or entry point. Check how repository permissions are requested and whether selected-repository access is supported. Done means users are not asked to grant access to all public repositories while the required selected-repository workflow still works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, typescript
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100