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

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Duplicates & near-duplicates 3 findings

What it is: Same function copy-pasted into multiple modules with minor variations.

Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.

How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.

Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.

3 matching findings on this repo

low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 3 places repo-level
low Near-duplicate function bodies in 4 places repo-level

View all duplicates & near-duplicates findings →

Legacy markers 1 finding

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

1 matching finding on this repo

low Old/deprecated-named symbol `_format_legacy` in AIAdvisor/skills/solr-opensearc…

View all legacy markers findings →

Commented-out code 27 findings

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

12 matching findings on this repo

info Commented-code block (5 lines) in migrationConsole/lib/console_link/tests/test_…
info Commented-code block (5 lines) in migrationConsole/lib/console_link/console_lin…
info Commented-code block (7 lines) in migrationConsole/lib/console_link/console_lin…
info Commented-code block (5 lines) in migrationConsole/lib/console_link/console_lin…
info Commented-code block (7 lines) in migrationConsole/lib/console_link/console_lin…
info Commented-code block (8 lines) in migrationConsole/lib/integ_test/integ_test/co…
info Commented-code block (7 lines) in migrationConsole/lib/integ_test/integ_test/ma…
info Commented-code block (11 lines) in migrationConsole/lib/integ_test/integ_test/f…
info Commented-code block (5 lines) in migrationConsole/lib/integ_test/integ_test/so…
info Commented-code block (7 lines) in migrationConsole/lib/integ_test/integ_test/te…
info Commented-code block (7 lines) in migrationConsole/lib/integ_test/integ_test/te…
info Commented-code block (5 lines) in migrationConsole/lib/integ_test/integ_test/te…

View all commented-out code findings →

Config drift 20 findings

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

12 matching findings on this repo

high [SEC088] Go: TLS InsecureSkipVerify=true: tls.Config{InsecureSkipVerify:true} d… AIAdvisor/opensearch-pricing-calculator/cluster/a…:34
high Phantom test coverage: test_empty_config_raises_value_error migrationConsole/lib/console_link/tests/test_clus…:350
high Phantom test coverage: test_from_workflow_config_no_config migrationConsole/lib/console_link/tests/test_envi…:294
high Phantom test coverage: test_empty_config_raises_unsupported_error migrationConsole/lib/console_link/tests/test_fact…:26
high Phantom test coverage: test_launch_scram_no_configmap_raises migrationConsole/lib/console_link/tests/test_kafk…:270
low File has no detected symbols: deployment/migration-assistant-solution/jest.conf…
low File has no detected symbols: deployment/cdk/opensearch-service-migration/jest.…
low File has no detected symbols: transformation/standardJavascriptTransforms/jest.…
low File has no detected symbols: orchestrationSpecs/jest.config.js
low File has no detected symbols: orchestrationSpecs/tsup.config.ts
low File has no detected symbols: orchestrationSpecs/packages/argo-workflow-builder…
low File has no detected symbols: orchestrationSpecs/packages/argo-workflow-builder…

View all config drift findings →

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.