wasmCloud

Projects that follow the best practices below can voluntarily self-certify and show that they've achieved an Open Source Security Foundation (OpenSSF) best practices badge.

There is no set of practices that can guarantee that software will never have defects or vulnerabilities; even formal methods can fail if the specifications or assumptions are wrong. Nor is there any set of practices that can guarantee that a project will sustain a healthy and well-functioning development community. However, following best practices can help improve the results of projects. For example, some practices enable multi-person review before release, which can both help find otherwise hard-to-find technical vulnerabilities and help build trust and a desire for repeated interaction among developers from different companies. To earn a badge, all MUST and MUST NOT criteria must be met, all SHOULD criteria must be met OR be unmet with justification, and all SUGGESTED criteria must be met OR unmet (we want them considered at least). If you want to enter justification text as a generic comment, instead of being a rationale that the situation is acceptable, start the text block with '//' followed by a space. Feedback is welcome via the GitHub site as issues or pull requests There is also a mailing list for general discussion.

We gladly provide the information in several locales, however, if there is any conflict or inconsistency between the translations, the English version is the authoritative version.
If this is your project, please show your baseline badge status on your project page! The baseline badge status looks like this: Baseline badge level for project 6363 is baseline-2 Here is how to embed the baseline badge:
You can show your baseline badge status by embedding this in your markdown file:
[![OpenSSF Baseline](https://www.bestpractices.dev/projects/6363/baseline)](https://www.bestpractices.dev/projects/6363)
or by embedding this in your HTML:
<a href="https://www.bestpractices.dev/projects/6363"><img src="https://www.bestpractices.dev/projects/6363/baseline"></a>


These are the Baseline Level 2 criteria. These are criteria version v2026.08.28.

Baseline Series: Baseline Level 1 Baseline Level 2 Baseline Level 3

        

 Basics

  • General

    Note that other projects may use the same name.

    wasmCloud is a cloud native platform for running WebAssembly workloads across any cloud, Kubernetes, datacenter, or edge.

    Using wasmCloud, you can run microservices, functions, and agents as ultra-dense, deny-by-default bytecode sandboxes that are far more secure and efficient than traditional containers.

    Please use SPDX license expression format; examples include "Apache-2.0", "BSD-2-Clause", "BSD-3-Clause", "GPL-2.0+", "LGPL-3.0+", "MIT", and "(BSD-2-Clause OR Ruby)". Do not include single quotes or double quotes.
    If there is more than one language, list them as comma-separated values (spaces optional) and sort them from most to least used. If there is a long list, please list at least the first three most common ones. If there is no language (e.g., this is a documentation-only or test-only project), use the single character "-". Please use a conventional capitalization for each language, e.g., "JavaScript".
    The Common Platform Enumeration (CPE) is a structured naming scheme for information technology systems, software, and packages. It is used in a number of systems and databases when reporting vulnerabilities.

 Controls 19/19 ●

  • Controls


    Enough for a badge!

    When a CI/CD task is executed with no permissions specified, the CI/CD system MUST default the task's permissions to the lowest permissions granted in the pipeline. [OSPS-AC-04.01]
    Configure the project's settings to assign the lowest available permissions to new pipelines by default, granting additional permissions only when necessary for specific tasks.

    Every workflow in .github/workflows declares a top-level permissions: block (contents: read by default), and jobs that need more request it explicitly at the job level. zizmor checks workflows for excessive permissions in CI.

    https://github.com/wasmCloud/wasmCloud/tree/main/.github/workflows


    Enough for a badge!

    When an official release is created, that release MUST be assigned a unique version identifier. [OSPS-BR-02.01]
    Assign a unique version identifier to each release produced by the project, following a consistent naming convention or numbering scheme. Examples include SemVer, CalVer, or git commit id.

    Each release is tagged with a unique Semantic Versioning identifier (vX.Y.Z), created once by the release workflow and never moved (https://github.com/wasmCloud/wasmCloud/blob/main/RELEASE_RUNBOOK.md#versioning-policy).


    Enough for a badge!

    When an official release is created, that release MUST contain a descriptive log of functional and security modifications. [OSPS-BR-04.01]
    Ensure that all releases include a descriptive change log. It is recommended to ensure that the change log is human-readable and includes details beyond commit messages, such as descriptions of the security impact or relevance to different use cases. To ensure machine readability, place the content under a markdown header such as "## Changelog".

    All releases include release notes as conventional commit comments, indicating what's breaking and what changes. Here's a newer release for example: https://github.com/wasmCloud/wasmCloud/releases/tag/v2.11.0 [release_notes]


    Enough for a badge!

    When a build and release pipeline ingests dependencies, it MUST use standardized tooling where available. [OSPS-BR-05.01]
    Use a common tooling for your ecosystem, such as package managers or dependency management tools to ingest dependencies at build time. This may include using a dependency file, lock file, or manifest to specify the required dependencies, which are then pulled in by the build system.

    https://github.com/wasmCloud/wasmCloud/blob/main/Cargo.toml [external_dependencies]

    Dependencies are obtained with each ecosystem's standard tooling: Cargo from crates.io (declared in workspace.dependencies, locked by Cargo.lock), Go modules (go.mod/go.sum), and GitHub Actions pinned by commit SHA. Dependabot tracks updates.

    https://github.com/wasmCloud/wasmCloud/blob/main/CONTRIBUTING.md#obtaining


    Enough for a badge!

    When an official release is created, that release MUST be signed or accounted for in a signed manifest including each asset's cryptographic hashes. [OSPS-BR-06.01]
    Sign all released software assets at build time with a cryptographic signature or attestations, such as GPG or PGP signature, Sigstore signatures, SLSA provenance, or SLSA VSAs. Include the cryptographic hashes of each asset in a signed manifest or metadata file.

    Release binaries and container image manifest digests are signed with GitHub artifact attestations (Sigstore Fulcio/Rekor, SLSA provenance) by the release workflow. Users verify them with gh attestation verify or cosign verify-blob-attestation; the Sigstore bundle is attached to each GitHub Release.

    Per security-insights.yml: repository.release.attestations predicate-uri includes slsa Comment says: "Release binaries, container images and WIT interface packages carry Sigstore-signed SLSA provenance. Verify with gh attestation verify --repo wasmCloud/wasmCloud.". [signed_releases]


    Enough for a badge!

    When the project has made a release, the project documentation MUST include a description of how the project selects, obtains, and tracks its dependencies. [OSPS-DO-06.01]
    It is recommended to publish this information alongside the project's technical & design documentation on a publicly viewable resource such as the source code repository, project website, or other channel.

    Per security-insights.yml: repository.documentation.dependency-management-policy=https://github.com/wasmCloud/wasmCloud/blob/main/CONTRIBUTING.md#dependencies

    CONTRIBUTING.md documents how dependencies are selected (prefer existing and foundation-hosted projects, active maintenance, license allowlist), obtained (crates.io, Go modules, SHA-pinned Actions) and tracked (Dependabot, cargo audit, cargo deny).


    Enough for a badge!

    The project documentation MUST include instructions on how to build the software, including required libraries, frameworks, SDKs, and dependencies. [OSPS-DO-07.01]
    It is recommended to publish this information alongside the project's contributor documentation, such as in CONTRIBUTING.md or other developer task documentation. This may also be documented using Makefile targets or other automation scripts.

    https://github.com/wasmCloud/wasmCloud/blob/main/CONTRIBUTING.md#development-environment

    We support using a standard Rust toolchain or using a devcontainer to make changes. CONTRIBUTING.md lists the prerequisites (Rust stable, the wasm32-wasip1/wasip2 targets, wasm-component-ld) and the commands to build from source and run the tests, including building the wasm test fixtures with cargo xtask build-fixtures.


    Enough for a badge!

    The project documentation MUST include a list of project members with access to sensitive resources. [OSPS-GV-01.01]
    Document project participants and their roles through such artifacts as members.md, governance.md, maintainers.md, or similar file within the source code repository of the project. This may be as simple as including names or account handles in a list of maintainers, or more complex depending on the project's governance.

    Per security-insights.yml: repository.documentation.governance=https://github.com/wasmCloud/wasmCloud/blob/main/GOVERNANCE.md


    Enough for a badge!

    The project documentation MUST include descriptions of the roles and responsibilities for members of the project [OSPS-GV-01.02]
    Document project participants and their roles through such artifacts as members.md, governance.md, maintainers.md, or similar file within the source code repository of the project.

    https://github.com/wasmCloud/wasmCloud/blob/main/GOVERNANCE.md#maintainers-structure

    GOVERNANCE.md describes the maintainer roles (org maintainers and per-area maintainer teams), their responsibilities, how maintainers are onboarded, step down or take leave, and how decisions are made at the org and project level.

    https://github.com/wasmCloud/wasmCloud/blob/main/CONTRIBUTION_LADDER.md


    Enough for a badge!

    The project documentation MUST include a guide for code contributors that includes requirements for acceptable contributions. [OSPS-GV-03.02]
    Extend the CONTRIBUTING.md or CONTRIBUTING/ contents in the project documentation to outline the requirements for acceptable contributions, including coding standards, testing requirements, and submission guidelines for code contributors. It is recommended that this guide is the source of truth for both contributors and approvers.

    https://github.com/wasmCloud/wasmCloud/blob/main/CONTRIBUTING.md#submitting-changes

    CONTRIBUTING.md sets the requirements for acceptable contributions: tests for new functionality, passing CI, the code style guidelines, documentation updates, Conventional Commit messages, DCO sign-off, and review by a code owner.

    Enforced via CI: https://github.com/wasmCloud/wasmCloud/blob/main/.github/workflows/wash.yml


    Enough for a badge!

    The version control system MUST require all code contributors to assert that they are legally authorized to make the associated contributions on every commit. [OSPS-LE-01.01]
    Include a DCO in the project's repository, requiring code contributors to assert that they are legally authorized to commit the associated contributions on every commit. Use a status check to ensure the assertion is made. A CLA also satisfies this requirement. Some version control systems, such as GitHub, may include this in the platform terms of service.

    All contributions require Developer Certificate of Origin sign-off (GOVERNANCE.md, DCO and Licenses). The DCO app checks every pull request for Signed-off-by on each commit.

    Example: https://github.com/wasmCloud/wasmCloud/pull/894/checks [dco]


    Enough for a badge!

    When a commit is made to the primary branch, any automated status checks for commits MUST pass or be manually bypassed. [OSPS-QA-03.01]
    Configure the project's version control system to require that all automated status checks pass or require manual acknowledgement before a commit can be merged into the primary branch. It is recommended that any optional status checks are NOT configured as a pass or fail requirement that approvers may be tempted to bypass.

    We report multiple automated test suites for each check-in. The main branch ruleset requires the gate and gate-audit status checks to pass before a pull request can merge; gate aggregates the CI test, lint and build jobs.


    Enough for a badge!

    Prior to a commit being accepted, the project's CI/CD pipelines MUST run at least one automated test suite to ensure the changes meet expectations. [OSPS-QA-06.01]
    Automated tests should be run prior to every merge into the primary branch. The test suite should be run in a CI/CD pipeline and the results should be visible to all contributors. The test suite should be run in a consistent environment and should be run in a way that allows contributors to run the tests locally. Examples of test suites include unit tests, integration tests, and end-to-end tests.

    We report multiple automated test suites for each check-in. Every pull request runs the automated test suites in GitHub Actions (Rust unit and integration tests, component fixtures, Go tests, Kubernetes end-to-end tests, and coverage), and the required gate check blocks merging on failure.


    Enough for a badge!

    When the project has made a release, the project documentation MUST include design documentation demonstrating all actions and actors within the system. [OSPS-SA-01.01]
    Include designs in the project documentation that explains the actions and actors. Actors include any subsystem or entity that can influence another segment in the system. Ensure this is updated for new features or breaking changes.

    https://wasmcloud.com/docs/overview/#the-architecture describes the high-level design (runtime-operator, hosts, NATS transport, workloads of components and services, interfaces, host plugins), with linked pages for each part. The Kubernetes deployment architecture is at https://wasmcloud.com/docs/kubernetes-operator/operator-manual/overview/, and the host's trust boundaries are in https://github.com/wasmCloud/wasmCloud/blob/main/THREAT_MODEL.md#trust-boundaries.

    SELF_ASSESSMENT.md (https://github.com/wasmCloud/wasmCloud/blob/main/SELF_ASSESSMENT.md#actors) lists the actors and the actions each performs.


    Enough for a badge!

    When the project has made a release, the project documentation MUST include descriptions of all external software interfaces of the released software assets. [OSPS-SA-02.01]
    Document all software interfaces (APIs) of the released software assets, explaining how users can interact with the software and what data is expected or produced. Ensure this is updated for new features or breaking changes.

    The external interfaces are documented: WIT interface definitions in the repository (wit/ and crates/wash-runtime/wit/) with an interfaces overview at https://wasmcloud.com/docs/overview/interfaces/, the Kubernetes CRD API reference at https://wasmcloud.com/docs/kubernetes-operator/api-reference/, Helm values at https://wasmcloud.com/docs/kubernetes-operator/operator-manual/helm-values/, and the wash CLI at https://wasmcloud.com/docs/wash/.


    Enough for a badge!

    When the project has made a release, the project MUST perform a security assessment to understand the most likely and impactful potential security problems that could occur within the software. [OSPS-SA-03.01]
    Performing a security assessment informs both project members as well as downstream consumers that the project understands what problems could arise within the software. Understanding what threats could be realized helps the project manage and address risk. This information is useful to downstream consumers to demonstrate the security acumen and practices of the project. Ensure this is updated for new features or breaking changes.

    SELF_ASSESSMENT.md is a security self-assessment following the OpenSSF template, backed by THREAT_MODEL.md (trust boundaries, security goals, known limitations) and Gemara capability and threat catalogs for the host in docs/security/. An independent audit by Trail of Bits through OSTIF was completed in October 2023.


    Enough for a badge!

    The project documentation MUST include a policy for coordinated vulnerability disclosure (CVD), with a clear timeframe for response. [OSPS-VM-01.01]
    Create a SECURITY.md file at the root of the directory, outlining the project's policy for coordinated vulnerability disclosure. Include a method for reporting vulnerabilities. Set expectations for how the project will respond and address reported issues.

    Per security-insights.yml: project.vulnerability-reporting.policy=https://github.com/wasmCloud/wasmCloud/blob/main/SECURITY.md Comment says: "Report privately through GitHub at https://github.com/wasmCloud/wasmCloud/security/advisories/new or by email to security@wasmcloud.com. Reports are acknowledged within 3 business days. Advisories are published as GitHub Security Advisories in the affected repository."


    Enough for a badge!

    The project documentation MUST provide a means for private vulnerability reporting directly to the security contacts within the project. [OSPS-VM-03.01]
    Provide a means for security researchers to report vulnerabilities privately to the project. This may be a dedicated email address, a web form, VCS specialized tools, email addresses for security contacts, or other methods.

    GitHub private vulnerability reporting is enabled on the repository, and reports can also be sent to the private security list security@wasmcloud.com, as SECURITY.md documents.


    Enough for a badge!

    The project documentation MUST publicly publish data about discovered vulnerabilities. [OSPS-VM-04.01]
    Provide information about known vulnerabilities in a predictable public channel, such as a CVE entry, blog post, or other medium. To the degree possible, this information should include affected version(s), how a consumer can determine if they are vulnerable, and instructions for mitigation or remediation.

    Vulnerabilities are published as GitHub Security Advisories with CVE identifiers where assigned (for example CVE-2022-21707), linked from SECURITY.md.



You can use tools and AI systems to propose changes via a simple URL, such as https://www.bestpractices.dev/en/projects/6363/choose/edit?osps_ac_01_01_status=Met&osps_ac_01_01_justification=GitHub+enforced. See our automation proposals system for how to do that. This data is available under the Community Data License Agreement – Permissive, Version 2.0 (CDLA-Permissive-2.0). This means that a Data Recipient may share the Data, with or without modifications, so long as the Data Recipient makes available the text of this agreement with the shared Data. Please credit Brooks Townsend and the OpenSSF Best Practices badge contributors.

Project badge entry owned by: Brooks Townsend.
Entry created on 2022-08-15 21:56:48 UTC, last updated on 2026-11-03 20:55:31 UTC. Last lost passing badge on 2023-11-02 18:23:16 UTC. Last achieved passing badge on 2023-11-02 18:38:53 UTC.