Add security governance files - #24
Merged
Merged
Conversation
… CODEOWNERS, .gitignore) - Apache-2.0 LICENSE (matches kagenti org standard) - SECURITY.md with vulnerability reporting process - CONTRIBUTING.md with dev setup and PR process - CODEOWNERS for review routing - .gitignore hardened with secrets, IDE, OS patterns Signed-off-by: Paolo Dettori <paolo.dettori@example.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds foundational security governance files to the repository:
Branch Protection (recommended, not auto-applied)
After merging, consider enabling on
main:check,DCO)Context
Phase 2 of repo orchestration (following CI in #23). Identified as a gap in the
scan report.
Assisted-By: Claude Code