Repository Deploy Key Cleanup: Remove Mirror Keys After Build Pipelines Move

Repository deploy key cleanup begins when CI, mirrors, or package publishing move but old SSH keys remain trusted on repositories. A deploy key can look harmless if it has not been touched recently, yet it may still grant read or write access outside the normal identity lifecycle.

For stale repository deploy keys for mirrors and build pipelines, the review has to connect risk acceptance, reachability, compensating controls, and the current owner. The useful output is a deploy key cleanup record with fingerprint map, job references, access risk, replacement auth, and final removal date: Move active jobs to replacement authentication before deleting deploy keys, keep proof of the security decision, and avoid letting breaking mirrors or leaving repository write access trusted after pipeline changes become the hidden default.

Key takeaways

• Review stale repository deploy keys for mirrors and build pipelines through Fingerprint map, Pipeline references, Access risk, not age alone.
• Use one full CI and release cycle plus mirror and package-publish schedules before deciding that quiet means unused.
• Start with the reversible move: move active jobs to replacement authentication before deleting deploy keys.
• Slow down when breaking mirrors or leaving repository write access trusted after pipeline changes is still plausible.
• Prevent repeat cleanup by making teams create deploy keys with owner, job, permission mode, and review date.

Map SSH Key Use

Start with one repository group across deploy keys, CI secrets, mirrors, package jobs, release branches, and SSH audit records. The best cleanup scope is small enough that owners can answer quickly but wide enough to include the attachments that make removal risky.

Field	Why it matters
Owner	Cleanup needs a person or team that can accept the decision
Current purpose	A short reason to keep the item, written in present tense
Last meaningful use	last use, permission scope, owner, rotation age, and reachable systems
Dependency evidence	audit logs, deployment references, identity provider records, and service owners
Risk if wrong	The outage, data loss, access failure, or rollback gap the review must avoid
Next action	Keep, reduce, archive, disable, remove, or investigate

Do not make the inventory larger than the decision. A short list with owners and evidence beats a perfect spreadsheet that nobody is willing to act on.

Deploy Key Evidence

The useful question is not “how old is it?” It is “what would break, become harder to recover, or lose accountability if this disappeared?” For repository deploy key cleanup for mirror jobs, collect enough evidence to answer that without relying on naming conventions.

Check	What to look for	Cleanup signal
Fingerprint map	Deploy key fingerprint, title, permission mode, created date, and repository coverage	The key no longer matches a current pipeline
Pipeline references	CI variables, SSH URLs, mirror jobs, package publish scripts, and release branches	No supported job uses the key
Access risk	Read/write mode, external host, maintainer ownership, and last successful SSH auth	The key grants unnecessary repository access
Replacement auth	GitHub App, OIDC, deploy token, machine user, or narrowed key	Automation can run with better lifecycle control

Use several signals together. Activity can miss monthly jobs and incident-only paths. Ownership can be stale. Cost can distract from security or recovery risk. The strongest case combines runtime data, dependency checks, owner review, and a rollback plan.

If the evidence conflicts, label the item “investigate” with a named owner and review date. That is still progress because the next review starts with a narrower question.

Example Deploy Key Review

Map SSH fingerprints to CI and mirror jobs before deleting repository deploy keys.

rg "git@|ssh://|DEPLOY_KEY|known_hosts" .github .gitlab scripts docs
rg "mirror|submodule|publish|release branch|deploy key" .github scripts docs
rg "$KEY_FINGERPRINT|$KEY_TITLE" security docs ci

Treat the output as a candidate list. Do not pipe these checks into delete commands; add owner review, dependency checks, and a rollback path first.

Move Pipelines Before Revoking

Use the least permanent move that proves the decision. In repository deploy key cleanup for mirror jobs, removal is only one possible outcome; reducing size, narrowing permission, shortening retention, archiving, or disabling a trigger may produce the same benefit with less risk.

• Move active jobs to replacement authentication before deleting deploy keys.
• Remove write-enabled keys before read-only keys when risk differs.
• Archive fingerprint and job evidence with the release pipeline migration.

Track the cleanup candidate with a simple priority score:

Score	Good sign	Bad sign
Impact	Meaningful spend, risk, toil, noise, or confusion disappears	The item is cheap and low-risk but politically distracting
Confidence	Owner, purpose, and dependency path are understood	The team is guessing from age or name
Reversibility	Restore, recreate, re-enable, or rollback path exists	Deletion would be the first real test
Prevention	A rule can stop recurrence	The same pattern will return next month

Start with high-impact, high-confidence, reversible candidates. Defer confusing items only if they get an owner and a date; otherwise “defer” becomes another word for keeping waste permanently.

Jobs That Still Clone or Push

Some cleanup candidates are supposed to look quiet. Do not rush these cases:

• Package publishing, mirrors, submodule checkout, and old release branches.
• Keys reused across several repositories.
• Self-hosted runners or vendor jobs that do not show in ordinary workflow search.

For these cases, use a longer observation window, explicit owner approval, and a staged reduction. The point is not to avoid cleanup; it is to avoid making the first proof of dependency an outage.

Run the Deploy Key Cleanup

Run repository deploy key cleanup for mirror jobs as a decision review, not an open-ended hygiene project.

1. Pick the narrow scope and export the candidate list.
2. Add owner, current purpose, last-use evidence, dependency checks, and risk if wrong.
3. Remove obvious false positives, then ask owners to choose keep, reduce, archive, disable, remove, or investigate.
4. Apply the least permanent useful change first.
5. Watch the signals that would reveal a bad decision.
6. Complete the final removal only after the review window closes.
7. Save a deploy key cleanup record with fingerprint map, job references, access risk, replacement auth, and final removal date.

For broader cleanup planning, use the cleanup library to pair this guide with related notes. If the cleanup has infrastructure impact, pair it with a visible owner, a rollback path, and a measurable business case. For infrastructure cleanup, the main cloud cost optimization checklist is a useful companion.

Prefer Managed Automation Auth

Prevention should change the creation path, not just the cleanup path. For repository deploy key cleanup for mirror jobs, the useful prevention fields are owner, expiry date, least-privilege scope, rotation schedule, and removal notes. Make those fields part of normal creation and review.

• Create deploy keys with owner, job, permission mode, and review date.
• Prefer short-lived or app-based authentication for CI where possible.
• Review deploy keys whenever pipelines, mirrors, or package publishing move.

The recurring review should be short: sort by impact, pick the unclear items, assign owners, and close the loop on anything nobody claims. If the review keeps producing the same class of candidate, fix the creation path instead of celebrating repeated cleanup.

Example Decision Record

Use a compact record so the cleanup can be reviewed later without reconstructing the whole investigation.

Field	Example entry for this cleanup
Candidate	Stale repository deploy keys for mirrors and build pipelines in source repositories, CI pipelines, package publishing jobs, mirrors, and SSH access records
Why it looked stale	Low recent activity, unclear owner, or no current consumer after the first review
Evidence checked	Fingerprint map, Pipeline references, and owner confirmation
First reversible move	Move active jobs to replacement authentication before deleting deploy keys
Watch signal	The metric, alert, job, route, query, or owner complaint that would show the cleanup was wrong
Final action	Keep, reduce, archive, disable, or remove after one full CI and release cycle plus mirror and package-publish schedules
Prevention rule	Create deploy keys with owner, job, permission mode, and review date

This record is intentionally small. If the decision needs a long narrative, the candidate is probably not ready for removal yet. Keep investigating until the owner, evidence, reversible move, and prevention rule are clear.

FAQ

How often should teams do repository deploy key cleanup for mirror jobs?

Use one full CI and release cycle plus mirror and package-publish schedules for the first decision, then set a recurring cadence based on change rate. Fast-moving non-production systems may need monthly review; slower systems can be quarterly if every unclear item has an owner and a review date.

What is the safest first action?

The safest first action is usually ownership repair plus evidence collection. After that, move active jobs to replacement authentication before deleting deploy keys. That creates a visible test before permanent deletion.

What should not be removed quickly?

Do not rush anything connected to package publishing, mirrors, submodule checkout, and old release branches. Also slow down when the cleanup affects recovery, compliance, customer-specific behavior, rare schedules, or security response.

How do you make the decision useful later?

Write the decision as a small operational record: candidate, owner, evidence, chosen action, watch signals, rollback path, final date, and prevention rule. That format helps future engineers, search engines, and AI assistants understand the cleanup without guessing.