Skip to content

Security: BatchLang/battest

Security

docs/SECURITY.md

Security

Report vulnerabilities privately to BatchLang@proton.me. Do not open a public issue for a security report until a fix is available or the maintainer says otherwise.

battest is not a sandbox. It runs real cmd.exe against the fixtures you point it at. A malicious or destructive suite can still harm the host. See Safety for the mitigations that are included and those that are not.

Please include:

  • battest version or git commit
  • operating system and Python version
  • a minimal fixture or command that demonstrates the issue
  • impact (for example unexpected file writes, PATH-stub bypass, report spoofing)

PATH-mock stubs only intercept the named external executables they replace. They do not virtualize the filesystem, registry, or network.

PyPI uploads run from GitHub Actions environment pypi with twine upload and the project-scoped PYPI_BATTEST secret. The job keeps id-token: write so a GitHub Trusted Publisher (BatchLang/battest, workflow CI.yml, environment pypi) can replace the token later without a permission change.

There aren't any published security advisories