Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Review aria-at app GitHub permissions #318

Closed
mfairchild365 opened this issue Aug 26, 2021 · 2 comments
Closed

Review aria-at app GitHub permissions #318

mfairchild365 opened this issue Aug 26, 2021 · 2 comments

Comments

@mfairchild365
Copy link

I think it would be good to review the ARIA-AT app GitHub permissions. For example, I don't think it needs to write access to my public repositories.

image

A screenshot of the requested permissions is attached.

  • Read/Write access to my public repositories
  • Read access to team discussions (why?)
  • Read access to organizations and teams (why?)
  • Read access to my email address (okay)

I'm very hesitant to allow these permissions until write access is removed.

@mfairchild365
Copy link
Author

@s3ththompson @mcking65 want to get this on your radar

@sinabahram
Copy link

Just want to add a +1. I was surprised at it asking for access not only to my public ones, but then also blanket asking for private organizations as well, of course with explicit grant flows. This has significant implications, and I actually am super-hesitant to grant the permissions given sensitive data. I did, but now regret doing so, but it was the only way I thought to get access, so this makes one choose between privacy/sensible permissions and access.

I actually don't understand why it needs access to anything, as the messaging just talks about loggin in with GitHub, not giving this project access to one's entire GitHub.

@howard-e howard-e linked a pull request Sep 17, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants