CI/CD Platform · View 05 of 22 · People and journeys
The finding
- The trough is Await run, and its cause is silence rather than slowness. A contributor told why their build is restricted is not frustrated; one told nothing assumes they are unwelcome.
- The restriction that costs them most is the read-only cache, which lengthens their build. That cost is accepted deliberately: a cache writable by a fork is a code-execution path into every trusted build that reads it afterwards.
What the platform gains
- No secret, publishing identity or cache-write credential ever reaches code the company has not reviewed.
- Egress is restricted to the mirror and source control, so a hostile build cannot exfiltrate what it did manage to read.
- The run re-executes as trusted at merge, so the artefact that ships was built under full credentials.
Risks
- Maintainers under deadline pressure will want a one-click "run with secrets" for a fork. That control is the single most dangerous feature this platform could ship and is deliberately absent.
