If you believe you have found a security vulnerability in agentpytest or any of its reserved sibling packages on PyPI, do not open a public GitHub issue. Instead, report it privately so we can fix it before it is disclosed.

Preferred: open a private advisory at https://github.com/piyushbhavsarr/agentpytest/security/advisories/new.

Alternative: email the maintainer at the address listed on the GitHub profile with the subject line agentpytest: security.

Please include:

• A description of the issue and the impact you believe it has.
• Steps to reproduce, including any proof-of-concept code.
• Affected version(s) — pip show agentpytest is sufficient.
• Your environment (Python version, OS) if relevant.
• Whether you intend to disclose publicly, and on what timeline.

We treat all reports in good faith and will not pursue legal action against researchers who follow this policy and act in good faith.

In scope:

• The agentpytest Python package on PyPI.
• The reserved sibling packages: agent-pytest, pytest-agent, agentpytest-core, agentpytest-cli.
• The GitHub repository piyushbhavsarr/agentpytest, including its CI workflows and release pipeline.
• Documentation that, if compromised, could mislead users into installing malicious packages.

Out of scope:

• Vulnerabilities in third-party dependencies (litellm, pytest, httpx, numpy, opentelemetry-sdk, etc.) — please report those upstream. We will, however, ship a release pinning a fixed version once one is available upstream.
• User misconfiguration of judges, API keys, or CI secrets.
• Issues that require already-compromised local credentials.

Steps taken to keep releases trustworthy:

• Trusted publishing (OIDC). Releases to PyPI are authenticated via short-lived OIDC tokens. No long-lived API tokens are stored anywhere. See .github/workflows/publish.yml.
• Manual approval gate. Every release requires explicit human approval in the pypi GitHub Actions environment before the upload step runs.
• Signed git tags. Release tags are signed with the maintainer's GPG key.
• Sigstore-signed artifacts. Release artifacts are signed via Sigstore by pypa/gh-action-pypi-publish and verifiable with cosign.
• Branch protection. main requires PR review and CI green; force-push is disabled.
• Dependency auditing. pip-audit and Dependabot run in CI on every change.
• Secret scanning. GitHub secret scanning is enabled on the repository.

Until 1.0.0, only the most recent minor release receives security updates. After 1.0.0, the two most recent minor releases will be supported.

We will publicly thank reporters in the security advisory and the changelog unless they request otherwise.