Skip to content

Commit 02f9c6c

Browse files
authored
Merge pull request #12 from dash14/docs/improve-readme-overview
Improve README overview section
2 parents 97cecd2 + fe019ce commit 02f9c6c

File tree

2 files changed

+4
-19
lines changed

2 files changed

+4
-19
lines changed

.github/workflows/test.yml

Lines changed: 0 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -7,15 +7,6 @@ on:
77
pull_request:
88
branches:
99
- main
10-
paths:
11-
- 'docker/**'
12-
- 'setup/**'
13-
- 'report/**'
14-
- 'test/**'
15-
- 'compose.yml'
16-
- 'compose.test.yml'
17-
- 'Makefile'
18-
- '.github/workflows/test.yml'
1910

2011
jobs:
2112
unit_test:

README.md

Lines changed: 4 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -11,19 +11,13 @@
1111
![license](https://img.shields.io/github/license/dash14/buildcage
1212
)
1313

14-
**A secure Docker build environment that prevents supply chain attacks by restricting outbound network access during image builds.**
14+
**Secure your Docker builds against supply chain attacks — restrict outbound network access to only the domains you allow.**
1515

16-
buildcage is a GitHub Actions-ready Docker container that runs a custom BuildKit builder. When you configure Docker Buildx to use buildcage as a remote builder, all network traffic from `RUN` steps in your Dockerfile is routed through an internal proxy that can log and block connections based on domain name.
16+
When you run `RUN npm install` or `RUN apt-get install` in a Dockerfile, those commands can reach any server on the internet — and you have no visibility or control over where they connect. A compromised dependency could silently exfiltrate your build secrets or phone home to an attacker's server.
1717

18-
You define a list of allowed domains, and only connections to those domains are permitted during builds — everything else is blocked.
18+
buildcage prevents this. You define a list of allowed domains, and only those connections are permitted during builds. Everything else is blocked.
1919

20-
*Think of it as a firewall for your Docker builds.*
21-
22-
## Why Use buildcage?
23-
24-
When you run `RUN npm install` or `RUN apt-get install` in a Dockerfile, these commands can connect to any server on the internet. **You have no visibility or control over where they connect.**
25-
26-
buildcage solves this by restricting outbound network access during builds to only the domains you explicitly allow.
20+
No Dockerfile changes required. No certificates to install. Works with any language or package manager.
2721

2822

2923
## How It Works

0 commit comments

Comments
 (0)