Repo access doens't stop people from injecting code into your repository. A pull request actually puts objects into your repo, but under a different ref than he

Repo access doens't stop people from injecting code into your repository. A pull request actually puts objects into your repo, but under a different ref than heads and tags. 1. Go to github, do a git clone 'repo' --mirror 2. cd to the bare repo.git and do a git show-ref and you will see all the pull requests in that repo. If any of those pull requests contained a duplicate hash, then in theory they would be colliding with your existing objects. But since git falls back to whatever was there first, I think it would be very challenging indeed to subvert a repo. You'd essentially have to find somebody who's forked a repo with the intention of submitting a PR, say, on a long running feature branch. You could then submit your PR based off hashes in their repo before they do, which would probably mean your colliding object would get preference. Its pretty far fetched, but the vector is non-zero.