| Version | Supported |
|---|---|
| 0.1.x | ✅ |
| < 0.1.0 | ❌ |
Please report security vulnerabilities by emailing security@coding-swarm.local (replace with actual email) or by opening a GitHub advisory if hosted on GitHub.
Running autonomous AI agents with --dangerously-skip-permissions inside Docker containers carries inherent risks:
- Container Escape: While we use standard Docker isolation, container escapes are theoretically possible. Do not run agents on sensitive production hosts without additional sandboxing (e.g., gVisor).
- Resource Exhaustion: Agents run in infinite loops. Use Docker resource limits (
--cpus,--memory) to prevent them from consuming all host resources. - Network Access: By default, agents may have network access. You can restrict this by passing
--network noneinconfig.docker.extra_args, but this will preventpip installor other network-dependent tasks.
We recommend running the swarm in an ephemeral VM or a dedicated sandbox environment.