Repository navigation
docs: document escalation to the CRA steward - #763
Merged
Merged
Conversation
Signed-off-by: Bailey Hayes <bailey@cosmonic.com>
MendyBerger
approved these changes
Nov 5, 2026
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
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.
Adds an Escalating to the CRA Steward section to CONTRIBUTING.md, matching wasmCloud/wasmCloud's.
This repository has its own CONTRIBUTING.md, so the policy in the monorepo and the org defaults never showed here. The section names the two events the security team escalates to the Linux Foundation at steward@linuxfoundation.org: actively exploited vulnerabilities and severe incidents. Everything else follows the security policy.
This follows the Linux Foundation's CRA readiness guidance. The stewardship statement in SECURITY.md and the reporting channel in Security Insights already cover this repository.