WEBVTT

1
00:00:00.000 --> 00:00:10.000
A connected repository provides scan findings. These project records are fictional. Monitoring needs separate setup.

2
00:00:10.000 --> 00:00:22.000
Two package references share one dependency finding. The view groups them with the relevant policy.

3
00:00:22.000 --> 00:00:33.000
An eligible repair enters the queue. This example enables automatic building and requires human merge review.

4
00:00:33.000 --> 00:00:45.000
Review the change and its evidence. Repository checks and required approvals still apply.

5
00:00:45.000 --> 00:00:55.000
The connected GitHub pipeline deploys the repair. A deployment record does not establish application health.

6
00:00:55.000 --> 00:01:08.680
A new scan checks both repaired package references. A failed scan preserves findings. Incident response stays with the agreed operator.