fregante/github-issue-link-status

personal access token should only use public_repo scope by default

Open

#67 opened on Nov 3, 2021

View on GitHubContributor guide
 (1 comment) (0 reactions) (0 assignees)JavaScript (22 forks)github user discovery
enhancementhelp wanted

Repository metrics

Stars
 (310 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Thanks for such a nice project!

From the security perspective, I think it had better to check only public_repo access by default when we click the Generate One link.

I in this case, we can replace the following link:

- https://github.com/settings/tokens/new?scopes=repo&description=GitHub%20Issue%20Link%20Status
+ https://github.com/settings/tokens/new?scopes=public_repo&description=GitHub%20Issue%20Link%20Status

Also, It's worth to mention if someone wants to use this extension in the private repositories, we can mention that by saying something like: "To use this extension in the private repositories, consider give repo scope to use."

Wdyt?

Screen Shot 2021-11-03 at 22 03 31

Screen Shot 2021-11-03 at 22 03 59

Contributor guide

Research direction
Investigate the current token generation URL in the codebase and update it from 'repo' to 'public repo' scope. Also add a note for private repos.
Tech stack
javascript
Domain
frontendsecurity
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitHub personal access tokens
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90