FAILED: Repository Linter Issue: rl-secret_rotation
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 41
- Forks
- 33
- Avg merge
- 18h 34m
- Merged PRs (30d)
- 19
Description
A violation against the SAP Open Source standards have been detected.
Rule: rl-secret_rotation
Message: The following GitHub Actions secret has not been rotated within the last 12 months:
- ARTIFACTORY_COMMON_USER
Recommended actions:
- Replace long-lived secrets with OIDC (OpenID Connect) tokens where possible
- For required static credentials (API keys, tokens), rotate them at least annually
- Review and remove any unused secrets
Description: Checks if all GitHub Actions secrets have been rotated within the last 12 months. Long-lived secrets should be replaced with OIDC tokens where possible, and required static credentials must be rotated annually.
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 with the rl-secret_rotation rule documentation and inspect the GitHub Actions configuration that uses ARTIFACTORY_COMMON_USER. Determine whether the secret can be replaced with OIDC, or rotate it if static credentials are required; done means the linter no longer reports the secret as older than 12 months.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100