opensearch-project/opensearch-migrations

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.

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

Scan timing: clone 6.02s · analysis 48.24s · 23.2 MB · GitHub API rate-limit (preflight)

opensearch-project/opensearch-migrations

https://github.com/opensearch-project/opensearch-migrations · scanned 2026-06-05 22:54 UTC (4 days, 8 hours ago) · 10 languages

790 raw signals (332 security + 458 graph) 7th percentile · Java · large (100-500K LoC) System graph score 68 (lower by 3)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

100.0% cov · 203 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	40.0	0.15	6.00
`security_score`	28.0	0.25	7.00
`testing_score`	100.0	0.20	20.00
`documentation_score`	91.0	0.15	13.65
`practices_score`	97.0	0.15	14.55
`code_quality`	36.6	0.10	3.66
Overall		1.00	64.9

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 16 High 59 Medium 36 Low 148 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 147 System graph 203 Crowd 0 Layer: Software 135 Cicd 25 Security 17 Quality 127 Api 1 Frontend 32 Network 1 Hardware 12

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 migrationConsole/lib/console_link/console_link/models/kafka.py

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 migrationConsole/lib/console_link/console_link/models/kafka.py:643; move to env var / secrets manager.

migrationConsole/lib/console_link/console_link/models/kafka.py:643

Possible secret in dev-tools/jenkinsdocker/config.yml

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 dev-tools/jenkinsdocker/config.yml:29; move to env var / secrets manager.

dev-tools/jenkinsdocker/config.yml:29

Possible secret in TrafficCapture/dockerSolution/src/main/docker/services.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 TrafficCapture/dockerSolution/src/main/docker/services.yaml:14; move to env var / secrets manager.

TrafficCapture/dockerSolution/src/main/docker/services.yaml:14

Possible secret in TrafficCapture/dockerSolution/src/main/docker/elasticsearchTestConsole/testDocumentQuery.py

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 TrafficCapture/dockerSolution/src/main/docker/elasticsearchTestConsole/testDocumentQuery.py:26; move to env var / secrets manager.

TrafficCapture/dockerSolution/src/main/docker/elasticsearchTestConsole/testDocumentQuery.py:26

Insecure pattern 'private_key_in_repo' in TrafficCapture/trafficCaptureProxyServer/build.gradle:88

GapSeverity.CRITICAL Layer.SECURITY score 0.550

Why: critical severity · OWASP-class risk

TrafficCapture/trafficCaptureProxyServer/build.gradle:88

Insecure pattern 'eval_used' in transformation/transformationPlugins/jsonMessageTransformers/jsonGraalTransformerBase/src/main/java/org/opensearch/migrations/transform/GraalTransformer.java:60

GapSeverity.HIGH Layer.SECURITY score 0.413

Why: high severity · OWASP-class risk

transformation/transformationPlugins/jsonMessageTransformers/jsonGraalTransformerBase/src/main/java/org/opensearch/migrations/transform/GraalTransformer.java:60

Insecure pattern 'tls_verify_false' in TrafficCapture/dockerSolution/src/main/docker/elasticsearchTestConsole/testDocumentQuery.py:90

GapSeverity.HIGH Layer.SECURITY score 0.413

Why: high severity · OWASP-class risk

TrafficCapture/dockerSolution/src/main/docker/elasticsearchTestConsole/testDocumentQuery.py:90

Insecure pattern 'tls_verify_false' in TrafficCapture/dockerSolution/src/main/docker/elasticsearchTestConsole/testDocumentGenerator.py:45

GapSeverity.HIGH Layer.SECURITY score 0.413

Why: high severity · OWASP-class risk

TrafficCapture/dockerSolution/src/main/docker/elasticsearchTestConsole/testDocumentGenerator.py:45

Dockerfile pipes a remote installer into a shell

GapSeverity.HIGH Layer.HARDWARE score 0.375

Why: high severity

AIAdvisor/skills/solr-opensearch-migration-advisor/setup/docker/claude/Dockerfile:28

#10

pull_request_target workflow appears to check out untrusted PR code

GapSeverity.HIGH Layer.CICD score 0.375

Why: high severity

.github/workflows/fix-dependabot-pipfile-hash.yml

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/5c32f884-8b05-4639-9d71-04d57464a622/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/5c32f884-8b05-4639-9d71-04d57464a622/

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.