You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+7-10Lines changed: 7 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,18 +53,15 @@ When you run `RUN npm install` or `RUN apt-get install` in a Dockerfile, these c
53
53
54
54
### Recommended for:
55
55
56
-
- Teams building Docker images in CI/CD environments
57
-
- Organizations with security compliance requirements (SOC 2, ISO 27001, etc.)
58
-
- Projects using public package registries (npm, PyPI, RubyGems, etc.)
59
-
- Anyone concerned about supply chain security
60
-
- Companies handling sensitive data or intellectual property
56
+
- **CI/CD pipelines pulling from public registries** — if your builds download packages from npm, PyPI, RubyGems, or other public sources, buildcage limits the blast radius of compromised packages
57
+
- **Builds that handle secrets** — if your Dockerfiles use build secrets, tokens, or credentials, buildcage prevents them from being exfiltrated to unauthorized servers
58
+
- **Teams that need network visibility** — if you need to know exactly which external services your builds contact, buildcage logs every outbound connection and can enforce an allowlist
61
59
62
60
### May not be necessary for:
63
61
64
-
- Builds that already run in completely offline environments
65
-
- Teams using only vetted, internal package repositories
66
-
- Simple static site builds with no external dependencies
67
-
- Projects where build speed is critical and security is less of a concern
62
+
- **Fully offline builds** — if your builds run in an air-gapped environment with no external network access
63
+
- **Internal-only registries** — if all dependencies come from vetted, internal repositories with no public package sources
64
+
- **No-dependency builds** — if your Dockerfile only copies files and never runs commands that fetch external resources
68
65
69
66
## Features
70
67
@@ -80,8 +77,8 @@ When you run `RUN npm install` or `RUN apt-get install` in a Dockerfile, these c
80
77
### Prerequisites
81
78
82
79
- Docker with BuildKit (buildx plugin)
83
-
- Docker Compose (for local usage)
84
80
- GitHub Actions runner with Docker support (for CI/CD usage)
0 commit comments