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.
Sign up free Scan another repo
66 of your 184 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 3.02s · analysis 8.12s · 10.9 MB · GitHub API rate-limit (preflight)

redhat-appstudio/infra-deployments

https://github.com/redhat-appstudio/infra-deployments · scanned 2026-06-05 13:25 UTC (5 days, 7 hours ago) · 10 languages

236 raw signals (148 security + 88 graph) 10th percentile · Go · small (2-20K LoC) System graph score 77 (lower by 17)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Combined
60.5
/100
Security checks
44
83 findings
System graph
77
100.0% cov · 21 findings
Critical
9
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 40.0 0.15 6.00
security_score 31.7 0.25 7.92
testing_score 80.0 0.20 16.00
documentation_score 76.7 0.15 11.51
practices_score 79.0 0.15 11.85
code_quality 69.4 0.10 6.94
Overall 1.00 60.2
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 9 High 55 Medium 8 Low 15 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 83 System graph 21 Crowd 0 Layer: Quality 30 Cicd 6 Software 53 Security 11 Api 1 Network 2 Frontend 1

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

#1
Possible secret in argo-cd-apps/base/member/optional/helm/rekor/rekor.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 argo-cd-apps/base/member/optional/helm/rekor/rekor.yaml:31; move to env var / secrets manager.
argo-cd-apps/base/member/optional/helm/rekor/rekor.yaml:31
#2
Possible secret in components/konflux-kite/base/external-secrets/database-secret.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 components/konflux-kite/base/external-secrets/database-secret.yaml:24; move to env var / secrets manager.
components/konflux-kite/base/external-secrets/database-secret.yaml:24
#3
Possible secret in components/konflux-operator/ci/openshift-overlay-e2e/ci-common.sh
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 components/konflux-operator/ci/openshift-overlay-e2e/ci-common.sh:79; move to env var / secrets manager.
components/konflux-operator/ci/openshift-overlay-e2e/ci-common.sh:79
#4
Possible secret in components/konflux-operator/ci/openshift-overlay-e2e/ci-common.sh
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 components/konflux-operator/ci/openshift-overlay-e2e/ci-common.sh:81; move to env var / secrets manager.
components/konflux-operator/ci/openshift-overlay-e2e/ci-common.sh:81
#5
Possible secret in components/kubearchive/production/base/database-secret.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 components/kubearchive/production/base/database-secret.yaml:27; move to env var / secrets manager.
components/kubearchive/production/base/database-secret.yaml:27
#6
Possible secret in components/kubearchive/staging/stone-stage-p01/database-secret.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 components/kubearchive/staging/stone-stage-p01/database-secret.yaml:26; move to env var / secrets manager.
components/kubearchive/staging/stone-stage-p01/database-secret.yaml:26
#7
Possible secret in components/kubearchive/staging/stone-stg-rh01/database-secret.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 components/kubearchive/staging/stone-stg-rh01/database-secret.yaml:26; move to env var / secrets manager.
components/kubearchive/staging/stone-stg-rh01/database-secret.yaml:26
#8
pull_request_target workflow appears to check out untrusted PR code
GapSeverity.HIGH Layer.CICD score 0.375
Why: high severity
.github/workflows/verify-pipelines-configs.yaml
#9
Privileged port 44 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in components/cluster-as-a-service/development/add-hypershift-params.yaml is a real port, change the binding to ≥1024 or run behind a proxy.
components/cluster-as-a-service/development/add-hypershift-params.yaml
#10
Privileged port 420 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in components/konflux-operator/ci/openshift-overlay-e2e/Dockerfile is a real port, change the binding to ≥1024 or run behind a proxy.
components/konflux-operator/ci/openshift-overlay-e2e/Dockerfile

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/e4073d0b-6e25-4181-ac51-c8ae54b701d6/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/e4073d0b-6e25-4181-ac51-c8ae54b701d6/

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.