If you discover a security vulnerability in qa-agent, please report it responsibly:

• GitHub Security Advisories: Report a vulnerability

Please include a clear description of the issue, steps to reproduce, and any relevant logs or screenshots. Do not open a public issue for security vulnerabilities.

We will acknowledge your report within 5 business days and provide an initial assessment. We aim to release a fix or mitigation for confirmed vulnerabilities as quickly as possible and will coordinate disclosure with you.

Only the latest release on the main branch is supported with security updates. We do not backport fixes to older versions.

Users and contributors should be aware of the following aspects of qa-agent's design:

Remote code execution during installation. The installer (bin/init.mjs) downloads and executes code from the arozumenko/browser-verify GitHub repository. You should review the installer behavior before running it and ensure you trust the source.

MCP server credentials. API keys and tokens for optional MCP server integrations are stored in .mcp.json. This file is gitignored by default. Do not commit credentials to version control. Rotate any keys that are accidentally exposed.

Browser automation via CDP. The agent uses Chrome DevTools Protocol for browser automation. CDP provides full control over a browser instance, including access to page content, cookies, and network traffic. Run browser automation only against applications and environments you own or have authorization to test.

Shell permissions. The agent is granted shell access including tools like curl. Be mindful of the commands and URLs referenced in agent configurations, particularly in untrusted or modified skill files.

In scope:

• Vulnerabilities in the installer (bin/init.mjs) and its download/execution logic
• Credential leakage through default configurations or templates
• Injection or code execution flaws in agent definitions, skill prompts, or reference files
• Supply chain risks in dependencies fetched during installation

Out of scope:

• Vulnerabilities in third-party MCP servers (report these to their respective maintainers)
• Vulnerabilities in the arozumenko/browser-verify repository (report directly to that project)
• Security issues in user-modified or custom agent/skill configurations
• General browser or Chrome/Chromium vulnerabilities

This project is licensed under the Apache License 2.0. See LICENSE for details.