English · 日本語
Bajutsu is pre-alpha. Security fixes are applied to the main branch only;
there are no released versions to back-port to yet.
Please report security issues privately — do not open a public issue or pull request, and do not disclose the details publicly until a fix is available.
Use GitHub's private vulnerability reporting: open the repository's Security tab and choose Report a vulnerability.
We aim to acknowledge a report within a few days (best effort) and will keep you informed of progress toward a fix. When you report, please include enough detail to reproduce the issue — affected commit, steps, and impact.
Bajutsu is a defensive end-to-end (E2E) testing tool for the iOS Simulator. A few project-specific points worth keeping in mind:
- API keys / secrets. Only the AI paths (
record,run --dismiss-alerts) needANTHROPIC_API_KEY. Never commit or share API keys; keep them in.env(gitignored). The deterministicrun/CI gate needs no secrets. - Captured evidence. Run artifacts under
runs/(screenshots, page sources, logs) can contain sensitive data from the app under test. Review them before sharing, attaching to a pull request, or uploading to CI. - AI is never the judge. The deterministic
rungate involves no LLM; AI is used only to author scenarios and investigate failures. Pass/fail comes solely from machine-checkable assertions.