@devries-cameron20 / composio Mirror · read-only / commits / beeea625a
Fork 0

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

Mirrored from https://github.com/Camo67/composio.git

Synced Nov 21, 16:00 UTC

ci(security): harden docs-agent-eval caller (Bugbot fixes) (#4199)

## Security fixes for the docs-agent-eval caller (Cursor Bugbot findings) Follow-up to #4158 (merged). Cursor Bugbot flagged two real issues on the App-token caller; both fixed here. Two other findings were already resolved in the merged version (noted below). **Fixed:** - **App token left on disk (Medium):** check out the private engine with `persist-credentials: false`. Otherwise `actions/checkout` writes the GitHub App installation token into `engine/.git/config`, and the eval then runs untrusted agent code with filesystem access on the same runner — which could read that token (read access to the private engine repo). The token is only needed for the one-time fetch. - **Non-docs previews start evals (Medium):** the `deployment_status` trigger now requires the `environment_url` to start with `https://docs-` (matching the label path's `docs-*` rule), so a non-docs `*.preview.composio.dev` deployment can't start or cancel a docs eval. **Already resolved in #4158 (stale Bugbot findings from the pre-App design):** - "Unrelated labels cancel evals" — the route job's `startsWith(…, 'run-docs-tests')` guard skips unrelated `labeled` events before anything enters the eval concurrency group. - "Eval token cannot read deployments" — `deployments: read` is set on both jobs. Informational check, non-blocking. No behavior change beyond the two hardening fixes. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

Soumya Medapati committed Aug 21, 2026 at 13:33 UTC beeea625ab620a8fbf057ae65be08c1d0fef0f89

No changes.