GitHub
Code quality
Connected repo is archived
Part of the Repository protection posture check · fix arrives as a guide
What it is
The repository connected for scanning is archived on GitHub — read-only and no longer maintained.
Why it matters
Findings against it cannot be fixed without unarchiving, so they accumulate as permanent noise in your report. It also suggests the connection points at something that is no longer the live codebase.
How to fix it
Disconnect the archived repository and connect the one that is actually deployed. If it is still in production despite being archived, unarchive it — a production service should be maintainable.
Run them all on your app
Connect your repo and your live services with read-only scopes. The first scan is free, and nothing changes without your approval.