FAILED: Repository Linter Issue: rl-secret_rotation
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 43
- Forks
- 22
- Avg merge
- 16h 25m
- Merged PRs (30d)
- 59
Description
A violation against the SAP Open Source standards have been detected.
Rule: rl-secret_rotation
Message: The following GitHub Actions secrets have not been rotated within the last 12 months:
- OSS_INDEX_SETTINGS_XML
- OSS_INDEX_SETTINGS_XML_V2
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 two secrets listed in the issue, OSS_INDEX_SETTINGS_XML and OSS_INDEX_SETTINGS_XML_V2, and review the linked GitHub hardening documentation. Confirm whether each secret is still required and whether OIDC can replace it; done means required credentials are rotated or replaced and the repository linter no longer reports rl-secret_rotation.
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
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100