Midburn / Midburn/midburn-devops
GitLeaks
Open
Nobody has claimed this yet.
security
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Run gitleaks to make sure our repos aren’t leaking secrets
https://github.com/zricethezav/gitleaks
Contributor guide
No contributing guide indexed for this repository
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
Review the Gitleaks project at the linked URL first; the issue does not name repository paths, CI entry points, or tests. Clarify which repositories and execution workflow are in scope, then define completion as scanning the selected repositories with an agreed secret-detection check.
Written by the indexing model from the issue text.
Assessment
- Domain
- devops, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100