AI Coding Agent Dependency Security: How to Review Package Changes

An agent can add a dependency in seconds.

That convenience also means a project can acquire an unnecessary or malicious package just as quickly.

Require explicit dependency changes

A dependency addition should be visible in the diff.

Do not let the agent silently install packages that never become part of the reviewed project state.

Use lockfiles

Lock dependencies to known versions and review changes to lockfiles.

This improves reproducibility and makes unexpected transitive changes easier to identify.

Run vulnerability checks

Automated scanners can identify known vulnerabilities, abandoned packages, and risky dependency versions.

They are not a replacement for review, but they provide useful baseline protection.

Prefer existing dependencies

Before adding a package, the agent should check whether the repository already provides the required functionality.

Fewer dependencies mean a smaller supply-chain surface.

Review install scripts

Some packages execute code during installation.

Treat package installation as code execution and perform it inside the sandbox rather than on a privileged host.

Final takeaway

Dependency changes deserve the same review discipline as source-code changes. Make additions explicit, lock versions, scan vulnerabilities, and keep installation inside an isolated environment.

Source: software supply-chain security principles.

Production implementation

A useful control model separates the coding agent into four capability layers: workspace access, command execution, external services, and release authority. An agent may need broad read access to source files while still having no access to production secrets or deployment credentials. Keeping these permissions separate makes the system easier to reason about and reduces blast radius.

Use an isolated runtime for commands and package installation. Keep network access restricted where possible, and make development credentials different from production credentials. Store workflow state outside the model context so a restart does not require the agent to reconstruct sensitive permissions from conversation history.

For changes that can affect customers, add a deterministic gate between the agent and release. CI should verify the artifact, security checks should inspect dependencies and secrets, and production promotion should use an explicit permission or approval policy.

Failure-mode testing

Test malicious or accidental behavior as well as normal coding tasks. Try path traversal, destructive shell commands, dependency installation, environment-variable inspection, access to unrelated repositories, production API calls, database mutations, and attempted deployment without approval. The sandbox and permission layer should block these actions regardless of what the model requests.

Also test ordinary failures: broken builds, flaky tests, unavailable package registries, expired credentials, deployment health-check failures, and partial database migrations. The agent should receive clear results and should not be able to bypass the trusted control layer by retrying with a different command.

Observability

Record workflow ID, agent identity, repository, branch, commands, changed files, dependency changes, test results, deployment target, approvals, and rollback events. Redact secrets and sensitive data. These records make code-agent incidents reviewable and help identify repeated failure patterns.

Final takeaway

A coding agent should be treated like an automated engineer with constrained authority. Give it enough access to complete the task, but keep execution, secrets, production data, and release authority behind deterministic controls.

Safe workflow architecture

A strong coding-agent workflow can be structured as: task intake → isolated workspace → repository inspection → proposed changes → command execution → automated verification → diff review → preview deployment → approval → production release. Each stage should have a defined permission boundary.

The agent should not be able to skip stages merely by asking for a different command. If production deployment requires approval, the deployment service should enforce that requirement even when the agent has already modified the repository successfully.

Use branch or workspace isolation for concurrent tasks. Two agents editing the same files at the same time can create confusing state and make review difficult. Give each task an isolated working tree or branch, then merge through the normal verification path.

Review checklist

Before accepting an agent-generated change, inspect the files changed, dependency additions, generated configuration, database migrations, authentication code, infrastructure changes, and test coverage. A small source diff can still introduce a large permission change through configuration.

Verify that secrets did not enter the diff, logs, artifacts, or generated files. Confirm that tests actually exercise the changed behavior instead of merely passing because the relevant path is untested.

Recovery

When an agent makes a bad change, preserve the workspace and execution logs before deleting it. Identify whether the failure came from model reasoning, tool permissions, infrastructure, dependency behavior, or an incorrect human requirement. Then fix the control that allowed the failure rather than only prompting the model to behave differently next time.

The objective is a workflow where one bad generation is recoverable and does not become a production incident.

Testing and incident response

Test the workflow with both ordinary and adversarial tasks. Attempt to read a forbidden path, access an unrelated repository, install an unapproved package, inspect hidden environment variables, reach a production endpoint, modify production data, and deploy without approval. The expected result is a deterministic block with an auditable reason.

Also test recovery: a failed build should return to a known workspace state; a failed deployment should trigger the documented rollback path; an exposed secret should trigger revocation; and a failed migration should not leave the application and schema on incompatible versions.

Keep these tests in CI or staging so the security boundary is rechecked when the agent runtime, permissions, or repository changes. The goal is not to trust the model more. It is to make model mistakes cheap and recoverable.

Final review

Before granting the agent access, confirm the permission boundary with a clean test account and a disposable repository. Verify that blocked operations remain blocked after retries, alternate commands, and workflow restarts. This final check catches permission gaps that a happy-path coding task will never reveal.