Kubescape adds recurring security scans and tightens repository workflows

Kubescape added automated weekly security baseline scans to five core repositories and hardened workflows across ten or more repositories, according to an OpenSSF case study. The Kubernetes security project reports passing Open Source Project Security Baseline Level Two and completing all six Security Slam badges. Contributors pinned GitHub Actions to specific commits and reduced workflow token permissions. Broader security changes included protections against CSV formula injection and tighter handling of registry credentials. These changes affect software that can run with privileged access in production Kubernetes clusters. Automated coverage currently spans five core repositories; documentation and architectural assessments still require maintainer review.