Repo and PR authority
A suggested diff, a repository write, an approved pull request and a merge are four different levels of authority. We check the branch rules, bot identities and permissions that apply to each one.
Industry
A coding assistant that begins by proposing a diff can end up running commands, swapping dependencies or kicking off a deployment. We trace that path across the developer machine, the repository and the build system, and note the credentials sitting at each step.
Included in the work
01
A suggested diff, a repository write, an approved pull request and a merge are four different levels of authority. We check the branch rules, bot identities and permissions that apply to each one.
Generated changes flow into workflow runs, package scripts and deployment jobs. We find the places where untrusted repository content could reach a privileged token or environment.
The proposed diff, the commands that ran, the tool calls, the reviews and the approvals should all trace back to the resulting commit or build. We also check who can stop a job and who can restore what it changed.
02
In an agreed repository or test environment we follow one normal change through the delivery process, then pair it with attempts at an unauthorized workflow edit, a secret read and a release action. For scoping we need the architecture and the intended permissions, not repository credentials.
Related services and resources
Next step