mvx_static_analysis

Name: mvx_static_analysis
Availability: InStock
Author: MultiversX

Analyze MultiversX Rust smart contracts and Go code for security vulnerabilities.

12|5|Updated Jan 28, 2026

Search Tags:#static analysis #security #go #auditing #rust #smart contracts #multiversx

Ready to run

npx skills add https://github.com/multiversx/mx-ai-skills --skill mvx-static-analysis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mvx_static_analysis
Source: https://github.com/multiversx/mx-ai-skills/tree/main/antigravity/skills/mvx_static_analysis
Command: npx skills add https://github.com/multiversx/mx-ai-skills --skill mvx-static-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of identifying common vulnerabilities and anti-patterns in MultiversX smart contracts and protocol code, ensuring higher security and reliability.

Core Features & Use Cases

Automated Code Scanning: Utilizes compiler, linters, grep, and Semgrep to find critical issues.
Pattern Identification: Detects unsafe Rust usage, floating-point arithmetic, non-deterministic Go patterns, and more.
Use Case: Before deploying a new smart contract, run this Skill to catch potential unwrap() panics, forbidden float usage, or non-validated token IDs, preventing costly errors.

Quick Start

Run the mvx_static_analysis skill to check the attached Rust smart contract code for critical vulnerabilities.

Frequently Asked Questions about mvx_static_analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I scan MultiversX Rust smart contracts for security vulnerabilities?▼

To scan MultiversX Rust smart contracts for security vulnerabilities, run static analysis using this tool to detect unsafe code, unwrap() panics, floating-point arithmetic, and unvalidated token IDs before deployment.

What common anti-patterns cause non-deterministic execution in Go protocol code?▼

Non-deterministic execution in Go protocol code is caused by anti-patterns like non-deterministic map iterations. Static analysis identifies these patterns to enforce deterministic execution and secure blockchain development.

Can I use static analysis to prevent unwrap() panics in Rust smart contracts?▼

Yes, you can use static analysis to prevent unwrap() panics in Rust smart contracts. The tool scans for panic-inducing methods and other unsafe Rust usage to catch costly errors before deployment.

How do I check MultiversX code for forbidden floating-point arithmetic?▼

To check MultiversX code for forbidden floating-point arithmetic, run static analysis using linters, grep, and Semgrep. This identifies critical float usage issues to ensure deterministic execution and adherence to best practices.

What is the best way to enforce deterministic execution in MultiversX protocol code?▼

The best way to enforce deterministic execution in MultiversX protocol code is running automated static analysis to identify non-deterministic Go patterns, unsafe Rust usage, and floating-point arithmetic.

Does static analysis catch unvalidated token IDs in MultiversX smart contracts?▼

Yes, static analysis catches unvalidated token IDs in MultiversX smart contracts. It scans the codebase using Semgrep and linters to identify anti-patterns and ensure secure token handling.