Skip to content

docs: add a repository security policy and record legacy releases - #764

Merged
ricochet merged 2 commits into
wasmCloud:mainfrom
vados-cosmonic:docs/osps-l3-doc-fixes
Nov 5, 2026
Merged

ricochet merged 2 commits into
wasmCloud:mainfrom
vados-cosmonic:docs/osps-l3-doc-fixes

Conversation

@vados-cosmonic

Copy link
Copy Markdown
Contributor

Doc fixes from the OSPS Baseline Level 3 scan:

  • Add a repository SECURITY.md with a secrets and credentials policy, and point Security Insights at it (OSPS-BR-07.02).
  • Add a Reviews section to CONTRIBUTING.md and declare it as the Security Insights review-policy (OSPS-GV-03.02).
  • State the dependency remediation thresholds and that dependency review findings must be fixed before each release (OSPS-VM-05.01, OSPS-VM-05.02).
  • Describe the security assessment as the threat model and attack surface analysis (OSPS-SA-03.02).
  • Record the wasmCloud 1.x releases as legacy releases without SBOMs (OSPS-QA-02.02).

Signed-off-by: Victor Adossi <vadossi@cosmonic.com>
@vados-cosmonic
vados-cosmonic requested review from a team as code owners November 5, 2026 18:26
…ing and VEX

Signed-off-by: Victor Adossi <vadossi@cosmonic.com>
@ricochet
ricochet merged commit 5bdd192 into wasmCloud:main Nov 5, 2026
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants