Home / Docs

DepWall docs

An install-time firewall for AI coding assistants. Version 0.5.3. 14 pages — start with Install.

Start

• Install

  Install DepWall and wire it into your shell and your agent. Node 20 or newer.

• Verdicts

  ALLOW, ASK and BLOCK — what each one means, the exit codes, and why uncertainty always resolves to ASK.

• Commands

  Every DepWall command: monitor and enforce modes, doctor, check, scan, and the MCP server.

Configure

• AI assistants (MCP)

  Register DepWall with your coding assistant so it can ask about a package before installing it.

• Deep scan

  LLM analysis of gray-zone packages for prompt injection, exfiltration and obfuscation. Escalate-only.

• Private registries

  Point DepWall at an internal mirror so a lockfile from it does not resolve to ASK.

• Shared cache

  Speed up checks for public packages with a signed shared verdict service. Private names never leave your machine.

• Browser extension

  See the verdict the gate would return on npm and PyPI package pages, and on install commands you find anywhere. It reports; it does not block.

• CI pipelines

  Gate a build on DepWall — copy-paste recipes for GitHub Actions, GitLab CI and Jenkins, and the exit codes they read.

Reference

• What leaves your machine

  Exactly what DepWall sends, where, and what each service can learn from it — including the case where your own code does leave.

• Coverage

  The 20 package managers DepWall gates, plus git, and how deep the check goes for each.

• Environment variables

  Every environment variable DepWall reads, and what each one changes.

• Limits

  What DepWall does not do. Install time is not runtime, and command reading is not shell emulation.

• Troubleshooting

  Prebuilt binaries, missing platform packages, shims that are not intercepting, and how to report a miss.