ci-autofix-reusable
Audited by Socket on Apr 21, 2026
2 alerts found:
Anomalyx2No explicit malware (reverse shell, obfuscation, hardcoded credentials, or exfiltration code) is present in the repository workflow YAML itself. However, this workflow grants an external LLM agent network access to CI logs and broad repository write permissions (git push, gh pr create, gh api). That creates a significant supply-chain risk: if the external model, its credentials, or the prompt/agent is compromised or misused, sensitive data could be exfiltrated and malicious or unwanted repository changes could be made. Use of this pattern should be carefully controlled (restrict tool scopes, sanitize logs, require human approval for PRs) to reduce risk.
SUSPICIOUS. The stated purpose matches CI auto-fix workflow generation and the visible commands are mostly proportionate, but the trust-critical behavior is hidden in REFERENCE.md. Because the generated workflow may run with write permissions, invoke Claude with repository secrets, and take autonomous PR/issue actions, the missing template prevents confirming safe action sources, pinning, and exact credential/data flows.