Is "Proto with Id" on JetBrains Marketplace Safe to Install?

yidayoung · jetbrains · v1.1.0

support @id tag for proto. add tag comment "@module_id = 1" at first line of proto file or change proto filename start with number then you can add id quick by this...

Risk Assessment

Analyzed
68.25
out of 100
HIGH

4 security findings detected across all analyzers

JetBrains plugin analyzed via plugin.xml configuration and static code analysis

Severity Breakdown

0
Critical
1
High
0
Medium
0
Low
0
Info

Finding Categories

1
Malware Signatures

YARA Rules Matched

1 rule
postinstall file manipulation

About This Extension

support @id tag for proto. add tag comment "@module_id = 1" at first line of proto file or change proto filename start with number then you can add id quick by this...

Detailed Findings

4 total

YARA Rule Matches

1 rule

Security Analysis Summary

Security Analysis Overview

Proto with Id is a jetbrains extension published by yidayoung. Version 1.1.0 has been analyzed by the Risky Plugins security platform, receiving a risk score of 68.25/100 (HIGH risk) based on 4 security findings.

Risk Assessment

This extension presents high security risk. Significant concerns were identified during analysis. It is not recommended for use in sensitive or production environments without thorough review.

Findings Breakdown

  • High: 1 finding(s)

What Was Analyzed

The security assessment covers multiple analysis categories:

  • Malware Detection: YARA rule matching against 2,400+ malware signatures
  • Secret Detection: Scanning for exposed API keys, tokens, and credentials
  • Static Analysis: Code-level security analysis for common vulnerability patterns
  • Network Analysis: Detection of suspicious network communications and endpoints
  • Obfuscation Detection: Identification of code obfuscation techniques

Developer Information

Proto with Id is published by yidayoung on the jetbrains marketplace. The extension has approximately 437 users.

Recommendation

This extension is not recommended for installation without thorough manual review. Consider alternatives with lower risk scores, or contact the developer to address the identified security concerns.

Frequently Asked Questions