The scenario
In Vulnverse v2, Supply Chain CI provides the information trail around software delivery. Build status, artifact browsing, package metadata and webhook intake form the public surface. Private context covers runners, secret references, release approvals and dependency provenance.
Examine the difference between seeing a build result and being authorized to influence a release. A participant can map the records involved in a pipeline, identify which information belongs with maintainers or approvers, and explain what evidence would substantiate a release integrity claim.
Public surfaces
Developers, package consumers and connected integrations reach the delivery pipeline through these routes; the configured exercise inventory sets the actual scope.
| Route | Surface | Context |
|---|---|---|
/ | build-status | Build status dashboard and release overview. |
/artifacts | artifact-browser | Artifact browser and release metadata facade. |
/packages | package-registry | Package registry facade with dependency metadata. |
/webhooks | webhook-intake | Webhook intake and integration event surface. |
Private systems
runner-fleetPrivate applicationPrivate runner fleet and job metadata simulation.
secrets-storePrivate dataBuild secret reference and rotation workflow data.
release-approvalsPrivate applicationRelease approval and signing workflow representation.
dependency-cachePrivate applicationDependency cache and provenance data store.
Exercise questions
- What separates public artifact metadata from private runner, secret and approval context?
- Which records connect a build, dependency, artifact and release approval in an investigation?
- Does a visible webhook or package route demonstrate executable behavior, or a represented workflow that needs a supporting observation?
What to hand in
Prepare an artifact and approval evidence map. Record provenance visible in the range, the access boundary under review and evidence still needed before claiming a compromised release path.
Records and evidence
Pipelines, artifacts, packages, webhooks, runner jobs and release approvals support software delivery information review. Treat secret records as lab references and do not substitute real credentials or connect the exercise to production build systems.
pipelinesartifactspackageswebhooksrunner-jobsrelease-approvals
Record each Supply Chain CI finding with the research method →