Priority risk
Secret in a workflow
HighReadyCodeGH-1184 · Code
A deploy token in CI still authenticates and is not locked to one repo.
- Tool
GitHub
- Impact
- CI deploy token authenticates and is not locked to one repo.
- Recommended next step
- Rotate the secret and scope it to the release environment only.
- Proven
- 13:48
- Kill action
- Rotate the secret
Evidence
- Found in .github/workflows/release.yml
- Token still returns 200 on api.github.com
- Not constrained by environment protection rules