Skip to content

Security: CodewithJha/mutiny

Security

SECURITY.md

Security Policy

Supported versions

Mutiny is under active development. Security fixes land on main first. There is no separate LTS branch yet.

Version / branch Supported
main (latest) Yes
Older commits / forks Best-effort

What Mutiny is (and isn’t)

Mutiny is a behavioral fuzz-testing engine for agents you own or are authorized to test. It is not an open-internet attack proxy. Default targets are local projects, in-process adapters, or localhost with sandboxed mock tools.

Reporting a vulnerability

Please do not open a public GitHub issue for security-sensitive reports.

  1. Prefer GitHub Security Advisories (private disclosure).
  2. Or email the maintainer via the contact options on the GitHub profile linked from this repository.

Include:

  • Affected package / path (mutiny_core, CLI, Hosted API/UI, adapter, …)
  • Steps to reproduce
  • Impact (data exposure, RCE on Hosted, policy bypass in the oracle, …)
  • Whether you have a suggested fix

We aim to acknowledge within 7 days and share a remediation plan when we have one.

Safe contribution rules

  • Do not commit secrets, API keys, or production credentials.
  • Do not add features that encourage testing third-party systems without attestation / authorization.
  • Prefer local / mock tools in examples and tests.

Scope notes for researchers

In-scope examples: flaws in policy evaluation, regression replay correctness, Hosted API auth gaps (when auth exists), dependency CVEs in this repo’s lockfiles.

Out of scope: using Mutiny to attack systems you do not own; social engineering of maintainers; DoS against GitHub infrastructure.

There aren't any published security advisories