From a finding to a verified fix.
Watch one maintenance workflow, from a repository finding through repair and verification.
This silent recording uses our interactive illustration with fictional project records. It shows the workflow, not a live customer system, a real scan or measured delivery time.
Transcript and scene descriptions
· Start with the running system
The portfolio shows fictional North Pole project records. A connected repository supplies scan findings. App URLs and an installed browser beacon supply limited monitoring signals; monitoring is separate from a repository scan.
· Inspect the finding
A fictional dependency advisory appears in two package references. The view groups the findings and shows the related published policy. Detecting a vulnerable dependency does not establish that it is reachable in production.
· Queue the repair
An eligible repair becomes an initiative in the delivery queue. The illustrated project allows automatic building and requires a person to review the merge. Actual behavior follows the configured controls.
· Review the change
The review compares the dependency change and its evidence. Repository checks and required approvals remain in force. Other permitted configurations may allow automatic merge; this illustration shows human merge review.
· Follow deployment
The connected GitHub pipeline executes deployment and its environment approvals. Taiga shows the resulting deployment record. A successful deployment record does not establish application health or resolution of the finding.
· Verify the repaired commit
A new scan checks both package references in the repaired commit. In this fictional outcome, the vulnerable version is no longer detected. A failed scan retains prior findings. The agreed operator remains responsible for incident response.
Check the scope in the documentation
Capabilities depend on repository access, configured build and merge settings, connected deployment pipelines and monitoring setup. The public documentation describes those requirements.