ghtier
← All scopes
Classic scope·part of repo

public_repo

Tier 2 · MediumData

Why Tier 2

Tier 2 because it reaches Repository creation: Write (repository), Contents: Write (repository), Deployments: Write (repository) and 1 more.

Same as repo, but only for public repositories. Write access to a widely used public repository is still a supply chain risk.

GitHub: Limits access to public repositories. That includes read/write access to code, commit statuses, repository projects, collaborators, and deployment statuses for public repositories and organizations. Also required for starring public repositories.

Available on: Every setup. Source

Permissions it reaches (6)

TierPermissionEvidence
T2sets tierContents: WriterepositoryStated by GitHub: Read/write access to code, commit statuses, repository projects, collaborators, and deployment statuses for public repositories.
T2sets tierDeployments: WriterepositoryStated by GitHub: Read/write access to code, commit statuses, repository projects, collaborators, and deployment statuses for public repositories.
T2sets tierRepository creation: Writerepository3 documented endpoints
  • POST /orgs/{org}/repos
  • POST /repos/{template_owner}/{template_repo}/generate
  • POST /user/repos
T2sets tierCommit statuses: WriterepositoryStated by GitHub: Read/write access to code, commit statuses, repository projects, collaborators, and deployment statuses for public repositories.
T3Administration: Readrepository1 documented endpoint
  • GET /repos/{owner}/{repo}/teams
T3Contents: Readrepository1 documented endpoint
  • POST /repos/{template_owner}/{template_repo}/generate