quay/mirror-registry

Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.

12 of your 44 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 1.19s · analysis 2.78s · 0.3 MB · GitHub API rate-limit (preflight)

https://github.com/quay/mirror-registry · scanned 2026-06-05 19:15 UTC (4 days, 17 hours ago) · 10 languages

74 raw signals (34 security + 40 graph) 29th percentile · Go · tiny (<2K LoC)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 17 hours ago · v2 · 35 actionable findings from 2 signal sources. 19 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

88.9% cov · 14 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	75.0	0.15	11.25
`security_score`	35.4	0.25	8.85
`testing_score`	85.0	0.20	17.00
`documentation_score`	61.0	0.15	9.15
`practices_score`	87.0	0.15	13.05
`code_quality`	78.8	0.10	7.88
Overall		1.00	67.2

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 4 High 11 Medium 10 Low 5 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 21 System graph 14 Crowd 0 Layer: Cicd 14 Quality 3 Software 6 Security 6 Api 1 Hardware 4 Frontend 1

Exclude dismissed / FP Exclude test files

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

Possible secret in ansible-runner/context/app/project/roles/mirror_appliance/tasks/upgrade-config-vars.yaml

GapSeverity.CRITICAL Layer.SECURITY score 1.000

Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in ansible-runner/context/app/project/roles/mirror_appliance/tasks/upgrade-config-vars.yaml:16; move to env var / secrets manager.

ansible-runner/context/app/project/roles/mirror_appliance/tasks/upgrade-config-vars.yaml:16

Possible secret in ansible-runner/context/app/project/roles/mirror_appliance/tasks/upgrade-config-vars.yaml

GapSeverity.CRITICAL Layer.SECURITY score 1.000

Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in ansible-runner/context/app/project/roles/mirror_appliance/tasks/upgrade-config-vars.yaml:26; move to env var / secrets manager.

ansible-runner/context/app/project/roles/mirror_appliance/tasks/upgrade-config-vars.yaml:26

Possible secret in ansible-runner/context/app/project/roles/mirror_appliance/tasks/secret-vars.yaml

GapSeverity.CRITICAL Layer.SECURITY score 1.000

Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in ansible-runner/context/app/project/roles/mirror_appliance/tasks/secret-vars.yaml:5; move to env var / secrets manager.

ansible-runner/context/app/project/roles/mirror_appliance/tasks/secret-vars.yaml:5

.env file present in repo: .env

GapSeverity.HIGH Layer.SECURITY score 0.750

Why: high severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from the file; move to env var / secrets manager.

pull_request_target workflow appears to check out untrusted PR code

GapSeverity.HIGH Layer.CICD score 0.375

Why: high severity

.github/workflows/extended-tests.yml

pull_request_target workflow appears to check out untrusted PR code

GapSeverity.HIGH Layer.CICD score 0.375

Why: high severity

.github/workflows/jobs.yml

No auth library detected

GapSeverity.MEDIUM Layer.SECURITY score 0.338

Why: medium severity

Docker base image uses a mutable or implicit tag: registry.access.redhat.com/ubi8:latest

GapSeverity.MEDIUM Layer.HARDWARE score 0.225

Why: medium severity

Dockerfile:11

Docker base image uses a mutable or implicit tag: registry.access.redhat.com/ubi8-minimal

GapSeverity.MEDIUM Layer.HARDWARE score 0.225

Why: medium severity

Dockerfile:77

#10

Docker base image uses a mutable or implicit tag: registry.access.redhat.com/ubi8:latest

GapSeverity.MEDIUM Layer.HARDWARE score 0.225

Why: medium severity

Dockerfile:84

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.

For AI agents + API integrations

Email me when this repo regresses

Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.

API access

This page is publicly accessible at: https://repobility.com/scan/6f2fb54f-3a0d-4b92-b3eb-ca3ad796244d/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/6f2fb54f-3a0d-4b92-b3eb-ca3ad796244d/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.