x/vgo: security of requiring github token #24055
Labels
Milestone
Comments
|
For the case of private repos, assuming they're in an organization, you could make a CI account that only has read permission to the repos. Beyond that, sure, it would be great if GitHub supported read-only oauth scopes. If so, vgo would happily use that token (it doesn't check which scopes are associated with the token). I'd love suggestions about what to do instead of the current github token but that seems to be the best github is offering right now. If you know of something different we can do, I'd be happy to listen. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version)?vgo
Does this issue reproduce with the latest release?
No, just with vgo.
Github oauth scopes do not exist such that you can read from multiple github repos, including private repos without also granting write permission for those repos. This is a security concern for automated build environments.
The text was updated successfully, but these errors were encountered: