cisagov / cisagov/skeleton-docker
Re-enable GitHub permissions monitoring when practical
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 22
- Forks
- 14
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 4
Description
💡 Summary
In #223 we disabled GitHub permissions monitoring because this functionality is poorly implemented and has been causing GitHub actions workflows to fail or hang due to the MITM implementation hogging or leaking memory. This functionality should be re-enabled when this becomes practical.
Motivation and context
It is useful to monitor GitHub permissions so ensure that we allow only the minimal required permissions. Once we can do so without unnecessary workflow failures we should.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing issue #223 and the GitHubSecurityLab actions-permissions monitor linked in this issue. Determine whether its MITM implementation can monitor GitHub permissions without causing workflows to fail or hang from memory use. Done means monitoring is re-enabled only once those workflow failures and hangs are avoided.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100