VS Code Marketplace Verified domain

TI Embedded Debug for VS Code

by Texas Instruments · 8.3K users
e6364cc8-8124-5d8d-9e6b-e273821aa514 | Store v0.6.0
31/ 100
LOW risk
No change since v0.5.2
AI review verdict
No high-risk signal observed

Based on the RiskyPlugins AI security review of the observed evidence. The review covers version 0.5.0, not the analysed version 0.6.0.

Analysis record

Analysed
1 week ago 13 November 2026
Version
v0.6.0
Artifact
SHA256 2ee8bb7d…11d213
Detail
Full list

Evidence ledger

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

8 findings

Publisher Evidence

Limited evidence

Texas Instruments

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

56
Publisher domain
ti.com
Observed
Store verification signal
No verified badge
Not verified
Extension portfolio
20
Portfolio

12 evidence rows available.

Finding Categories

AI Security Report

AI Security Review

Evidence context: threat category none; evidence quality strong.

The TI Embedded Debug for VS Code extension is designed to debug Texas Instruments embedded devices using OpenOCD and GDB. The extension's filesystem and process access requirements are fully justified by this purpose. Dependencies like tar@^7.4.0, extract-zip@^2.0.1, and @microsoft/vscode-file-downloader-api@^1.0.1 in /extension/package.json are legitimate requirements for downloading and managing toolchains. Version management dependencies (semver@^7.7.3, compare-versions@^6.1.1) support toolchain versioning, which is standard for embedded development tooling.

The four high-severity YARA findings are all known false-positive patterns. The YARA--postinstall_system_command match in /extension/CHANGELOG.md is a documentation file, not executable code. The same rule match in /extension.vsixmanifest is a metadata manifest file. The YARA--postinstall_crypto_operations and YARA--NoUseWeakRandom findings in /extension/dist/extension.js are in bundled, minified JavaScript output—this is webpack or esbuild build output that naturally triggers code-smell YARA rules. The postinstall_* rules are documented false positives that match basic Node.js patterns for file operations and crypto, while NoUseWeakRandom is a code-quality rule that fires on standard JavaScript.

Critically, the findings summary shows zero actual threat indicators: no IoC matches, no malware signatures, no network exfiltration patterns, no obfuscation findings, and no credential theft patterns. The threat_indicators field confirms "ioc":"0","malware-signature":"0","malware":"0","network":"0","obfuscation":"0". The 21 high-severity findings are all code-smell rules that inflated the count without representing actual threats.

The strongest counterargument is the high severity rating on the YARA findings. However, severity labels on code-smell rules do not indicate actual malicious behavior. These rules are designed to catch suspicious patterns, but they fire on legitimate Node.js development patterns, especially in bundled code. The extension has 5,479 users and is from ti-development-tools, indicating it's a legitimate tool from Texas Instruments. No findings target actual secrets like .env files, SSH keys, or cloud credentials. No findings show workspace file reads combined with external network calls for exfiltration. The findings are entirely consistent with a legitimate embedded development tool that downloads and manages toolchains.

Key Reasons

  • YARA code-smell rules triggered on bundled dist/extension.js and documentation files
  • Zero actual threat indicators (ioc:0, malware:0, obfuscation:0)
  • Dependencies match legitimate toolchain management purpose
  • postinstall_* and NoUseWeakRandom are documented false-positive patterns

False Positive Considerations

  • YARA code-smell rules on standard Node.js patterns
  • Bundled/minified JavaScript in dist/extension.js
  • Documentation files (CHANGELOG.md, vsixmanifest) triggering executable rules
  • Finding count inflation from code-smell rules

Reviewed 2026-05-23 · version 0.5.0; recommended action: suppress false positive; model confidence 85%.

VS Code version history

Risk trend by version

5 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
31
Change since first
-40
Change from previous
No change
Versions:
First analyzed version
0.4.0
First seen Nov 4, 2025
Risk range
31 to 71
Across analyzed versions
Latest analyzed version
0.6.0
First seen Nov 13, 2026
Selected version
low
Version
v0.6.0
First seen 1 week ago
Risk score
31
Findings
8
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

Debug TI devices using OpenOCD and GDB

Frequently Asked Questions