Understand freshness and recover a failed sync
Repository access, inventory revision, advisory refresh, and response status each have their own clock.
Check the right timestamp
The repository’s current branch, the last imported commit, and the last advisory assessment may differ. A source advisory also has its own published and modified timestamps. None of those dates establishes when an attack on your systems began.
Use the project’s inventory revision and last successful sync to understand what was assessed. Use source collection status to understand how current the intelligence check is. Use response activity to understand the actions you recorded.
Recover repository access
Failed imports retain the last successful snapshot and show the failure. A missing branch, revoked permission, or unavailable provider must not appear as a clean assessment.
- Check whether the provider connection needs to be reauthorized.
- Confirm that the repository is still selected in the GitHub App or accessible to your GitLab identity.
- Confirm that the selected branch and inventory path still exist.
- Reconnect or update selection, then request another sync.
Handle an intelligence-source outage
Retry after a temporary source failure and inspect the source status again. Continue investigating previously reported findings. An unsuccessful source request does not invalidate known evidence, and a new collection time alone is not a newly discovered vulnerability.
For time-sensitive decisions, follow the linked vendor or maintainer guidance directly and record what you checked.