C# by ReSharper
The AI review rates the findings as likely false positive. The risk score (77/100) comes from stored counts that the review could not adjust. A new analysis will update it.
Analysis record
- Analysed
- 11 months ago 1 December 2025
- Version
- v0.0.15
- Artifact
- SHA256 2248e037…8dbca0
- Detail
- Counts only, rows expired
Latest version 2026.3.1 has not been analysed yet. Score and findings are for version 0.0.15.
Detail for this analysis has expired
This analysis ran on 1 December 2025. 139 findings counted, and the counts are kept. The individual rows have aged out of storage. A new analysis restores them.
Detail for this analysis has expired
This analysis ran on 1 December 2025. 2,563 network indicators counted, and the counts are kept. The individual rows have aged out of storage. A new analysis restores them.
Publisher Evidence
HighJetBrains
Publisher identity, store signals, distribution reach, and warning signals used for context. Treat this as supporting evidence, not a clean bill of health.
12 evidence rows available.
Detail for this analysis has expired
This analysis ran on 1 December 2025. 2,702 findings counted, and the counts are kept. The individual rows have aged out of storage. A new analysis restores them.
Stored counts by category
- 2,563
- Network indicators
- 115
- Code patterns
- 115
- Malware signatures
- 17
- Dependencies
- 7
- Network calls
AI Security Report
AI Security Review
Evidence context: threat category none; evidence quality moderate.
The extension reads source files and invokes language‑server processes, which matches its purpose of providing code analysis, completion, and refactoring for C#. The only filesystem‑related findings are the dependency listings in package.json (e.g., DEP‑inversify, DEP‑glob) and no child‑process execution is detected in the activation code, so the access is justified. Network activity is limited to several NET‑FETCH calls in extension/dist/extension.js (lines 511, 82602, 82725, 82913, 93517, 95403, 100401). These fetches are typical for downloading language‑server binaries or telemetry endpoints and do not target credential files. No secret‑type findings (e.g., reads of .env, .ssh, cloud credential files) are present, and the secret category report is empty. The strongest counterargument could be that the numerous code‑smell findings (high‑severity low‑impact rules) indicate malicious intent. However, all code‑smell detections are triggered by ordinary JavaScript patterns within the bundled dist/ assets, which are known to generate false positives, and none correspond to actual malicious behavior. Consequently, the evidence points to normal extension functionality rather than wrongdoing.
Key Reasons
- Filesystem reads correspond to source analysis, matching the extension’s declared functionality
- Network fetches are confined to bundled JavaScript and resemble standard language‑server updates
- No secret or credential‑access findings were reported
- High‑severity code‑smell alerts are recognized as noise from bundled dependencies
False Positive Considerations
- code‑smell findings on bundled JavaScript
- dependency enumeration in package.json
- generic fetch calls in minified dist files
Reviewed 2026-05-23 · version 0.0.15; recommended action: no action; model confidence 85%.
Source Code Not Available
Source code is not available for this version of the extension.
About This Extension
Frequently Asked Questions
Similar Extensions
Related extensions from the same publisher or marketplace