QWED

Type to search pages, engines and advisories.

    Looking for API details?Search the docs

    Security

    Handled in the open

    QWED is a security boundary, so its own security is handled in the open. Here are the answers a security or procurement review asks for, the project’s track record, and how to report a vulnerability.

    What happens next

    • Acknowledged
    • Triaged
    • Fixed
    • Published

    Track record

    • 40advisories published, across 8 packages
    • 39 of 40fixed in a released version
    • 5reported by outside researchers, 7 credited by name
    • 21releases in the last 90 days, across all packages

    Counted at every build from the published advisories on GitHub and the release history on PyPI.

    For security and procurement reviews

    QWED is designed for environments where human oversight and an audit trail are required. It does not, by itself, make a system compliant with any regulation.

    Where it runs

    In your environment, as a Python library, a CLI, a self-hosted API or a Docker image. The exception is QWED Security: a GitHub App hosted on Google Cloud (Cloud Run), which processes the webhook and API traffic needed to scan a pull request.

    What leaves your systems

    Nothing is sent by QWED itself. Checks that start from natural language send a prompt to the model provider you configure; with a model you host, nothing leaves your infrastructure.

    What decides

    Deterministic engines such as SymPy, Z3, SQLGlot and AST analysis. The model never approves its own output: it only translates natural language, and that translation is not itself verified.

    Separation of duties

    The model proposes, QWED checks, and your system enforces the decision. QWED returns ADMIT or DENY; your integration acts on it, or a QWED product does, as QWED Security does by failing the pull request check.

    Evidence you keep

    Every result carries its status and admission decision. A VERIFIED result carries a proof_ref, a SHA-256 commitment to its evidence. Verification Context v1.0 is the open format for keeping a result as a record. The specification

    Versions and fixes

    Security fixes ship for the latest release only (qwed 9.1.x today). Every fixed vulnerability is published with its affected and fixed versions. Latest advisories

    Continuity

    QWED has a single maintainer, and no backup maintainer has been appointed yet. What exists for continuity

    Licence and limits

    Apache-2.0, for every package. What QWED does not check is written down, package by package. What QWED does not verify

    What went wrong

    Every advisory, sorted by what failed. The first two are the failures that matter most for a verification project, so they are counted on their own rather than left inside the list. Each advisory explains the cause and the fix.

    The proof engines are also tested at every release on claims with a known answer: the latest results.

    No fixed version yet for @qwed-ai/legal 1.0.0 (GHSA-mrv2-8596-cx34).

    • A check returned VERIFIED for a claim that was false16
    • A guard let through something it should have stopped6
    • Untrusted input could run code5
    • Untrusted input could exhaust compute1
    • Not yet sorted12

    Latest advisories

    Every fixed vulnerability is published as a GitHub security advisory on the affected repository, and listed here.

    All 40 advisories

    Report a vulnerability

    Please don’t report vulnerabilities in public issues, pull requests or discussions. Use one of these private channels.

    What happens next

    1. 01

      Acknowledged

      We aim to reply within 3 business days. QWED has a single maintainer, so it may occasionally take longer.

    2. 02

      Triaged

      The report is reproduced and validated as quickly as possible.

    3. 03

      Fixed

      You are kept informed while it is investigated and fixed.

    4. 04

      Published

      Disclosure timing is agreed with you, then the advisory is published with the fix.

    Coordinated disclosure

    Please allow reasonable time to investigate and fix the issue before you disclose it. In particular:

    • Don’t disclose publicly until a fix or mitigation is available.
    • Make a good-faith effort to avoid privacy violations, data destruction and service disruption.
    • Don’t access, change or take data beyond what you need to demonstrate the issue.

    Supported versions

    qwed 9.1.x (latest release)
    Supported
    qwed < 9.1
    Not supported. Please upgrade.

    Security fixes are released for the latest version only.

    Security issue or bug?

    Security issue

    Compromises confidentiality, integrity or availability: code execution, injection, auth bypass, privilege escalation, sensitive data exposure, sandbox escape, or a check that fails open.

    Report it privately

    Bug

    A defect with no security impact, such as a wrong calculation that is not reported as VERIFIED, a documentation problem or a crash that can’t be exploited. A wrong result reported as VERIFIED is a security issue.

    Report it on the issue tracker

    How releases are protected

    • Every QWED package on PyPI is published through PyPI Trusted Publishing, with build provenance attestations.
    • Two-factor authentication is enforced for the whole QWED-AI organisation on GitHub, and required for anyone with write access to PyPI or Docker Hub.
    • QWED Security is installed across the QWED-AI organisation and checks pull requests before they merge.

    Credit

    Reporters who disclose responsibly are credited publicly in advisories and release notes, unless they ask to stay anonymous. Everyone credited so far is listed on the community page.