Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,7 @@ Thank you for your interest in contributing to the wasmCloud TypeScript ecosyste
- [Pull Request Process](#pull-request-process)
- [Dependencies](#dependencies)
- [Code Scanning](#code-scanning)
- [Escalating to the CRA Steward](#escalating-to-the-cra-steward)
- [Releases](#releases)
- [Working with wasmCloud](#working-with-wasmcloud)
- [Debugging](#debugging)
Expand Down Expand Up @@ -290,6 +291,22 @@ the repository's Security tab.
critical, 14 days for high and 90 days for medium severity. Low severity alerts are fixed on a
best-effort basis.

## Escalating to the CRA Steward

The wasmCloud security team escalates two kinds of event to the Linux Foundation, wasmCloud's CRA
steward, at steward@linuxfoundation.org:

- **Actively exploited vulnerabilities:** a vulnerability in this repository's examples or
templates for which the security team has reliable evidence that a malicious actor has exploited
it.
- **Severe incidents:** a security compromise of the project's own infrastructure, such as its
GitHub organization, release pipeline, signing identities, or published artifacts.

A vulnerability with no evidence of exploitation is not an escalation event and follows the normal
process in the [security policy](https://github.com/wasmCloud/typescript/security/policy).
Remediation never waits on the escalation decision. The same policy covers all of wasmCloud; see
[wasmCloud's CONTRIBUTING.md](https://github.com/wasmCloud/wasmCloud/blob/main/CONTRIBUTING.md#escalating-to-the-cra-steward).

## Releases

Each stable wasmCloud release starts the [Release](.github/workflows/release.yml) workflow with
Expand Down
Loading