Skip to content

Security: baldaworks/sddx

Security

SECURITY.md

Security policy

Supported versions

SDDX is published from this repository as a Go CLI. Security fixes target the current main-line development version (0.1.x / 0.1.0-dev until a stable release series is tagged). Always build or install from a known commit and keep Callee on a supported 0.16.x line.

What SDDX trusts

SDDX coordinates local repository state and invokes:

  • Git (read-only visibility probes; never SDDX-owned stage/commit/push),
  • Callee (provider-backed workflows on a controlling TTY),
  • a configured graph adapter process,
  • configured check argv.

Provider credentials, Callee permissions, and Git ignore/index policy are operator-owned. SDDX does not install or authenticate providers. Human approval is a separate authority boundary from agent semantic acceptance.

Reporting a vulnerability

Please report security issues privately rather than opening a public issue with exploit detail.

  1. Email the maintainers using the contact address on the GitHub organization or repository security advisory channel for baldaworks/sddx.
  2. Include: affected version or commit, environment (OS, Go, Callee version), reproduction steps, and impact assessment.
  3. Allow a reasonable window for a fix before public disclosure.

If the GitHub Security Advisories feature is enabled for the repository, prefer filing a private advisory there.

Non-vulnerabilities

The following are intentional product boundaries, not security defects:

  • Requiring a human to run sddx approve and to authorize provider runs.
  • Refusing to edit .gitignore or to stage/commit on the operator's behalf.
  • Exiting with domain code 1 for lifecycle blockers (missing artifacts, stale approval).
  • Executing configured check or adapter argv exactly as declared in project configuration (operators must treat those argv as trusted configuration).

Supply chain

  • Prefer building from source with a pinned Go toolchain (go.mod).
  • Callee release-contract tests (when run) validate a specific npm package provenance for @baldaworks/callee@0.16.1; see CONTRIBUTING.
  • Review changes to internal/agentpack/assets/ and installed .callee/sddx/ content carefully; doctor enforces lock and workflow byte identity.

There aren't any published security advisories