CI and release risk

Unsafe Workflow Automation

Agents that can edit workflows, package scripts, deploy files, or release automation can turn small mistakes into production risk.

Severity: CriticalDetected by: Pro

Signals CapitalGuard looks for

GitHub Actions or CI files editable by agent workflows

Package lifecycle scripts with network or shell actions

Deployment scripts near secrets or production credentials

A workflow change can run automatically with more authority than the developer expected.

Lifecycle scripts can execute during install, build, test, or deploy.

Release automation often touches secrets, infrastructure, and customer-facing systems.

Require code-owner review for workflow and release files.

Block agent edits to deployment and package lifecycle scripts by default.

Separate read-only analysis from commands that mutate infrastructure or publish artifacts.

Next step

Related threats

Agent instruction risk

Hidden instructions in docs, issues, prompts, logs, and internal notes can influence coding agents when those files become task context.

AI tools do not need to print raw keys to create risk; file paths, variable names, logs, and configuration context can reveal how systems are wired.

Some files should not be read, edited, summarized, or sent to external tools by autonomous coding agents.