OpenVSX Registry Store verified

Elastic Docs Utilities

cf6c665e-6106-5792-94ed-8bf95d4eb7dd | Store v0.18.0
48/ 100
MEDIUM risk
No change since v0.17.1
AI review verdict
Review before use

The AI review rates the findings as likely false positive, but the risk score (48/100) still counts them. The review covers version 0.17.1, not the analysed version 0.18.0.

Analysis record

Analysed
5 months ago 26 May 2026
Version
v0.18.0
Artifact
SHA256 bdfeb5b8…f85f90
Detail
Full list

Evidence ledger

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

4 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.

50
Publisher domain
No domain
Missing
Store verification signal
Verified publisher
Verified
Extension portfolio
1
Portfolio

13 evidence rows available.

Finding Categories

3
Network

AI Security Report

AI Security Review

Evidence context: threat category none; evidence quality moderate.

Elastic Docs Utilities, version 0.17.1 on OpenVSX, is an extension from Elastic — a well-known and verified developer of open-source tooling. It has 4,227 users and is described as 'Utilities for Elastic Docs authoring.' The evidence shows no findings that deviate from expected IDE extension behavior.

Filesystem and process access: The evidence bundle contains zero findings related to filesystem access, process spawning, secret reading, or credential theft. There are no code-smell, secret, manifest-analysis, or tool-poisoning` findings at all. The extension's access appears limited to what is necessary for its stated documentation utility purpose.

Network activity: Four medium-severity network findings are present — two socket_io calls at extension/out/extension.js:54 and extension/out/extension-web.js:148, and two fetch calls at extension/out/extension.js:240 and extension/out/extension-web.js-232. For a documentation-authoring tool, socket-based communication and fetch requests are standard patterns. Socket.IO is commonly used for real-time preview functionality, and fetch calls are expected for retrieving documentation assets or update checks. Neither finding targets suspicious or unexpected endpoints.

Dependency surface: A single low-severity dependency finding references yaml@^2.8.4 in /extension/package.json. YAML parsing is directly relevant to a documentation utility that likely processes Elastic docs in YAML or frontmatter format. This is a routine, justified dependency.

Credential and secret access: Zero secret-access findings exist. There is no evidence the extension reads .env files, SSH keys, .git/config, or any credential store.

Strongest counterargument: An analyst might note that Socket.IO connections could theoretically be used to exfiltrate workspace content to an arbitrary server. However, this is a well-known open-source publisher with a documented product purpose, a mature version (0.17.1), and 4,227 users. The absence of any exfiltration-related findings — no file reads paired with network sends, no obfuscated payloads, no postinstall hooks — makes this theoretical concern unsupported by the evidence.

Key Reasons

  • Publisher is Elastic, a well-known open-source company
  • Zero malware signatures, IoCs, obfuscation, secret-access, or tool-poisoning findings
  • Network calls (Socket.IO, fetch) are consistent with documentation authoring functionality
  • YAML dependency is directly justified by the extension's stated purpose
  • No files from /dist/ — findings are from the extension's own entry points, yet they are benign

False Positive Considerations

  • Network call findings are inherent to any networked IDE extension
  • Socket.IO is a standard real-time communication library, not inherently suspicious

Reviewed 2026-05-24 · version 0.17.1; recommended action: no action; model confidence 88%.

Open VSX version history

Risk trend by version

4 analyzed versions. Each point is the latest successful scan for that version; failed zero-score scans are hidden. Dates: First seen by Risky Plugins.

Selected
48
Change since first
-1
Change from previous
No change
Versions:
First analyzed version
0.16.1
First seen Mar 15, 2026
Risk range
48 to 50
Across analyzed versions
Latest analyzed version
0.18.0
First seen May 26, 2026
Selected version
medium
Version
v0.18.0
First seen 5 months ago
Risk score
48
Findings
4
Change vs previous
No change

Pick any point on the chart, then open the Source tab to read that version's code.

Source Code Viewer

Source Code Not Available

Source code is not available for this version of the extension.

About This Extension

Utilities for Elastic Docs authoring

Frequently Asked Questions