OpenAgentPack is currently in public beta. Security fixes target the latest published beta of @openagentpack/cli, @openagentpack/sdk, and @openagentpack/playground, as well as main. Reporters should reproduce against the latest available version when possible.

The beta may contain breaking API or configuration changes before 1.0. Security support does not imply API stability.

Do not open a public GitHub issue for security vulnerabilities.

Instead, report privately through GitHub's private vulnerability reporting: open the repository's Security tab and click Report a vulnerability.

Please include:

• A description of the vulnerability and its impact.
• Steps to reproduce, or a proof of concept.
• Affected package and version.
• Any suggested remediation, if you have one.

We aim to acknowledge reports within a few business days and will keep you updated on remediation progress. Please give us reasonable time to release a fix before any public disclosure.

OpenAgentPack manages credentials as a first-class concern, so please keep these expectations in mind when reporting or contributing:

• Secrets belong in the environment, not the config. agents.yaml references secrets with ${VAR_NAME} and resolves them from .env at runtime. Never commit resolved secret values.
• .env and state files are gitignored (.env, .env.*, *.state.json, agents.state.json). Do not force-add them, and do not paste their contents into issues, PRs, or logs.
• Vault credentials are a security boundary. They are managed by the provider and are not written into local state in plaintext. Report any code path that leaks a credential into logs, state, or telemetry.

If you believe a secret has been committed to the repository history, treat it as a vulnerability and report it privately.