🐛 Fix inaccurate claims in security self-assessment#4348
Conversation
- Secret scanning: clarify it's GitHub repo-level, not CI/CD integrated - Container scanning: clarify it's planned, not yet in CI/CD pipeline Signed-off-by: Andrew Anderson <andy@clubanderson.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
✅ Deploy Preview for kubestellarconsole canceled.
|
|
👋 Hey @clubanderson — thanks for opening this PR!
This is an automated message. |
There was a problem hiding this comment.
Pull request overview
Updates the security self-assessment to remove inaccurate statements about current CI/CD-based secret and container scanning, clarifying what is enabled today vs. planned.
Changes:
- Corrected “Secret scanning” to reflect GitHub repository-level secret scanning (not CI/CD integrated yet)
- Updated “Container Scanning” to indicate it’s planned and not yet part of CI/CD
- Adjusted “Secret Detection” entry to align with repository-level scanning and planned CI/CD integration
|
Thank you for your contribution! Your PR has been merged. Check out what's new:
Stay connected: Slack #kubestellar-dev | Multi-Cluster Survey |
|
Post-merge build verification passed ✅ Both Go and frontend builds compiled successfully against merge commit |
Summary
These were flagged during review of the self-assessment before submitting to the CNCF TOC repo (cncf/toc#2106).
Test plan