🚨 Action Required: Repository Scheduled for Archival from 2 July 2025 🚨

[SkyDevSecOps-SCMA]

⚠️ GitHub Code Repositories you own are being archived starting 2 July 2025

What’s Happening ?

To better enable incident management, vulnerability management, and source code management, we have been asking developers to map their repositories to Service Configuration Items (CI) within the Heimdall platform. Heimdall is an internally developed platform that allows Sky developers to view code-related vulnerabilities identified in the scanning of their repositories.

We launched our Repo Mapping Campaign in early October and reached out on several occasions with instructions and reminders to complete the process of mapping your repositories to a Service CI. Last month, we sent out a final request to complete the mapping process and advised that unmapped repositories would be archived.

This repository has not yet been mapped was required by 11 June 2025. As your repositories remain unmapped, they are now scheduled to be archived from 2 July 2025.

Why Are We Doing This?

This mapping is essential for accurately managing Sky source code and ensuring clear linkage to Sky services, enhancing our overall security efficiency and incident management capabilities.

Action Required

To prevent archival, you will need to complete the mapping following the instructions below:

1. Navigate to the Heimdall platform. Note: You will need to be connected to the corporate VPN if not working from a Sky site.
2. Click "Login Heimdall / Request Access" to be directed to the corresponding repository in Heimdall.
3. In the "Primary Service CI" field, search for the relevant Service Name by starting to type the service name.
4. Select the correct Service Name from the search results.
5. In the confirmation popup, verify that the service details are accurate, then click "Save".
6. Once the mapping is complete, fill out the GitHub Repository Unarchiving request form by 2 July 2025. Note: The affected repository still be archived if the form is not filled.

If a repository cannot be mapped to a service for a valid reason, please provide a support group with an appropriate justification. This option enables the repository to be mapped directly to the relevant support group instead of a service CI. Only use this option if your code repository cannot be linked to an existing or new Service CI. Choosing this option will initiate periodic attestation requirement.

Need Assistance?

Contact our Slack channel #software-security-support for further assistance

Thank you for your attention to this matter and for helping us keep Sky safe and secure.

Sky Cyber Security