Security Policy

The BenchWeave SDK is pre-1.0 software maintained by a single person. This policy is written to be honest about that rather than to promise more than it can deliver.

Reporting a vulnerability

Please report privately, not in a public issue.

Use GitHub’s private vulnerability reporting: Report a vulnerability. It creates a private advisory. Only you and the maintainer can see it. It also handles coordinated disclosure and CVE requests if the process gets that far.

If you can, include:

  • The SDK version or commit you tested
  • Which surface is affected: the plugin contract packages, the Python runtime support, or the preview server used to develop plugins against recorded gateway sessions
  • What an attacker gains, and what access they need to start
  • The smallest reproduction you can manage

The maintainer acknowledges reports and works on them on a best-effort basis. This policy makes no promise about response time. If someone actively exploits an issue, say so in the report. The maintainer will treat it accordingly.

Please give the maintainer a reasonable chance to ship a fix before you disclose publicly. Credit in the advisory is gladly given. Say how you want the credit to read. You can also say that you do not want credit.

Scope

Supported version: the latest release. The SDK is pre-1.0. The project does not backport fixes to older tags.

In scope: anything that lets a plugin or a crafted input exceed the boundary that the SDK is meant to enforce:

  • The plugin contract the SDK implements, where a defect lets a plugin exceed the boundary a conforming gateway enforces
  • The preview server: anything that lets a recorded session or a crafted replay read or write outside its working directory
  • Secrets or tokens that leak through logs, errors, or preview-server responses

Out of scope:

  • Anything that requires an attacker to already have filesystem or operating-system access to the host. The SDK is local development tooling for single-operator use and does not defend against a compromised machine.
  • Missing TLS or hardening headers. The preview server binds to loopback (127.0.0.1) by default and ships no TLS. If you rebind it, you must provide transport security yourself.
  • Denial of service through sheer volume against a server you control.
  • Findings from automated scanners with no demonstrated impact.

Known weaknesses

The SDK is pre-1.0 and has rough edges. The project already knows about some of them and tracks them as public issues. If you find something already tracked, a comment on that issue is more useful than a new report. If you think the issue is more severe than its rating says, say so privately. Re-rate the severity rather than defend the rating.