When you start using DeepSource, you will need to explicitly grant DeepSource permission through your source code hosting provider to checkout your public and private repositories. To perform analysis, we checkout your code from supported source code hosting providers.
read:user
- Grants read access to a user’s profile data.
user:email
- Grants read access to a user’s email addresses.
Scope: https://docs.github.com/en/developers/apps/scopes-for-oauth-apps#available-scopes
.deepsource.toml
.
Application page: https://github.com/apps/deepsource-io GitHub Marketplace: https://github.com/marketplace/deepsource-io
Note: DeepSource will either raise a pull request or commit to a pull request with existing changes. The app will not make any code changes to the default branch of the repository. Reference: https://github.com/apps/deepsource-autofix
api
- Grants complete read/write access to the API, including all groups and projects, the container registry, and the package registry.
read_user
- Grants read-only access to the authenticated user’s profile through the /user API endpoint, which includes username, public email, and full name. Also grants access to read-only API endpoints under / users.
read_repository
- Grants complete read/write access to the API, including all groups and projects, the container registry, and the package registry.
Reference: https://docs.gitlab.com/ee/integration/oauth_provider.html#authorized-applications
vso.code_write
- Grants the ability to read, update, and delete source code, access metadata about commits, changesets, branches, and other version control artifacts. Also grants the ability to create and manage pull requests and code reviews and to receive notifications about version control events via service hooks.
vso.code_status
- Grants the ability to read and write commit and pull request status.
vso.project
- Grants the ability to read projects and teams.
Reference: https://learn.microsoft.com/en-us/azure/devops/integrate/get-started/authentication/oauth?view=azure-devops#scopes
account
.
Reference: https://developer.atlassian.com/cloud/bitbucket/bitbucket-cloud-rest-api-scopes/
account
.
pullrequest
.
issue
.
Reference: https://developer.atlassian.com/cloud/bitbucket/bitbucket-cloud-rest-api-scopes/ Atlassian Marketplace: https://marketplace.atlassian.com/apps/1222731/deepsource
account
.
repository:write
permissions, giving write access to the pull request’s destination repository. This is necessary to facilitate merging. Scope: pullrequest:write
.
repository
or repository:write
permissions. It gives access to only the admin features of a repository, not direct access to its contents. Of course, this can be (mis)used to grant read access to another user account who can then clone the repository, but apps that need to read or write source code would also request explicit read or write permissions for the concerned repository. Scope: repository:admin
.
repository:admin
scope is required to check the possibility of a commit. For this purpose, we use the branch restrictions API which requires this scope to function.Reference: https://developer.atlassian.com/cloud/bitbucket/bitbucket-cloud-rest-api-scopes/ Atlassian Marketplace: https://marketplace.atlassian.com/apps/1223705/deepsource-autofix