github query safe-waters/docker-lock: Could not resolve to a Repository with the name 'safe-waters/docker-lock'.
Action Required
Update the URL if the resource moved
Remove the entry if permanently unavailable
Add to config/exclude.yaml if a known false positive
Investigate GitHub API/auth failures when present
Auto-generated by awesome-docker ci broken-links
Originally created by @github-actions[bot] on GitHub (Mar 7, 2026).
Original GitHub issue: https://github.com/veggiemonk/awesome-docker/issues/1260
# Broken Links Detected
- Broken links: 0
- Redirected links: 0
- GitHub API errors: 1
## GitHub API Errors
- `github query safe-waters/docker-lock: Could not resolve to a Repository with the name 'safe-waters/docker-lock'.`
## Action Required
- Update the URL if the resource moved
- Remove the entry if permanently unavailable
- Add to `config/exclude.yaml` if a known false positive
- Investigate GitHub API/auth failures when present
---
*Auto-generated by awesome-docker ci broken-links*
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @github-actions[bot] on GitHub (Mar 7, 2026).
Original GitHub issue: https://github.com/veggiemonk/awesome-docker/issues/1260
Broken Links Detected
GitHub API Errors
github query safe-waters/docker-lock: Could not resolve to a Repository with the name 'safe-waters/docker-lock'.Action Required
config/exclude.yamlif a known false positiveAuto-generated by awesome-docker ci broken-links