Dependency Firewall offer: 50% off the base fee. See pricing

AI Coding Agents

A coding agent installs packages without anyone checking the name or the version. Dependency Firewall checks each install against the rules your security team sets, on every machine the agent runs on.

Today agents install packages that nobody has checked

A coding agent with shell access runs npm install, pip install or cargo add as part of a task. The model wrote the name and the version, and the install ran before a person read the diff.

The version an agent installs varies
An agent does not always take the latest version. It can pin one it has seen before, pick the newest release, or follow a release age setting on that machine.
Names that were never published
Some of the names a model writes do not exist. Anyone can register such a name afterwards.
A package manager setting covers one machine
A minimum release age in a config file applies on that machine or in that project. A developer can override it to get a newer version, and so can an agent told to make a failing install pass.

Check every package an agent installs

An agent installs with the same package managers as a developer. Once they point at the firewall, the same rules apply on any machine, whether a person or an agent ran the command.

A token per agent
Give agents their own access token, so the log shows which installs came from an agent.
Configuration in the project
Commit the client configuration, such as .npmrc or pip.conf. Every clone and every agent workspace then installs through the firewall.
Names that do not exist
A name that was never published fails as not found. A name that someone registered yesterday is inside the delay window.
Web proxy chaining
An agent behind your company web proxy needs no registry setting. The web proxy hands its installs to the firewall, even when it ignores the project configuration.

Only the registry URL changes. Nothing is installed on developer machines.Supported ecosystems

Agents work with the bsfw CLI

An agent runs the Dependency Firewall CLI itself. It lists the blocked installs, follows the log live while an install runs and reads each entry as JSON. Before an install it can look up the vulnerability and malware findings for an exact version.

A blocked install comes with its reason

A blocked version fails the install with the same error a developer would get. The log records the package, the version, the rule and the token that asked.

Who works with it

Security teams
Set the delay, the vulnerability threshold and malware blocking on a baseline firewall. They apply wherever an agent runs.
Developers
Work with the agent as before. When an install fails, the log names the rule, for you and for the agent.
Platform engineers
Keep access tokens in environment variables, outside the committed configuration.

Questions

Do agents need a setup of their own?

No. Agents use the same package managers as developers, so they read the same client configuration.

Can an agent switch the rules off?

No. The rules are set in the firewall, and an inherited rule cannot be removed on the firewall that inherits it.

Can an agent find out why an install failed?

Yes. With the bsfw CLI it reads the log entry for the blocked request, which names the rule. It can then pick a version that passes.

How do we tell an agent's installs from a developer's?

Give agents their own access token. The log records the token with every install.

Try it on one registry

Point one package manager at Dependency Firewall and check the log after the next install. The trial runs 14 days.