JetBrains Marketplace Store verified

Elasticsearch Java Client Examples Autocomplete

by elastic · 145 users
77f894f5-8f32-5ee8-8dbe-f14da9108840 | Store v1.0-SNAPSHOT
20/ 100
LOW risk
Risk verdict
No high-risk signal observed

Score-based assessment (low risk, 20/100). An AI review is available in the AI review tab.

Analysis record

Analysed
Today 22 November 2026
Version
v1.0-SNAPSHOT
Artifact
SHA256 94f44f99…e746bd
Detail
Full list

Is Elasticsearch Java Client Examples Autocomplete safe?

This is an autocomplete plugin for the Elasticsearch Java client, published on the JetBrains marketplace by Elastic. It suggests method names and example snippets as you write Elasticsearch API calls in Java. The plugin declares no special permissions, and it asks for no network or host access. The network endpoints listed for it, things like gf.gs and rsaj.hm, come from a scanner that pulled short strings out of the plugin's bundled files rather than from any address the plugin contacts.

The one flagged code pattern is a rule called YARA--postinstall_crypto_operations, and it matched inside docs-java-client-idea-plugin/lib/kotlin-stdlib-2.2.0.jar. That jar is the Kotlin standard library, a component that ships with nearly every Kotlin-based IntelliJ plugin. The rule fires on generic cryptography and process handling baked into the library, so the match describes the library itself rather than anything the plugin's authors wrote or anything that runs when you install.

The scanner also flagged eleven strings as domains, including pom.properties, which is the name of a Maven metadata file. Others, like nĵ.tj and nbս.sa, contain letters that no real domain can have. Nothing in the findings reads .env files, SSH keys, or cloud credentials, and nothing carries file contents off your machine.

The flags all trace back to the Kotlin library this plugin depends on and to strings the scanner misread. Developers using the Elasticsearch Java client can install it.

Evidence ledger

Ranked by severity · findings with a source location link to the code viewer

6 findings

Publisher Evidence

Low

elastic

Publisher identity, store signals, distribution reach, and warning signals used for context. Treat this as supporting evidence, not a clean bill of health.

77
Publisher domain
elastic.co
Observed
Store verification signal
Verified publisher
Verified
Extension portfolio
6
Portfolio

12 evidence rows available.

Finding Categories

AI Security Report

AI Security Review

Evidence context: threat category none; evidence quality weak.

The supplied findings do not establish what behavior triggered the matches. A fresh analysis with the relevant code and surrounding context is needed. These findings neither establish malicious behavior nor demonstrate that the extension is safe.

Key Reasons

  • Insufficient implementation context for the supplied findings

Reviewed 2026-11-10 · version 1.0-SNAPSHOT; recommended action: reanalyze; model confidence 97%.

About This Extension

Experimental IntelliJ IDEA Plugin to provide inline autocompletion for the Elasticsearch Java Client with examples from the documentation.

Frequently Asked Questions