input-validation

Name: input-validation
Availability: InStock
Author: PurpleAILAB

Detect input validation vulnerabilities in Solidity smart contracts.

60|18|Updated Jan 21, 2026

Search Tags:#input validation #secure coding #vulnerability detection #smart contract security #web3 security #solidity auditing

Ready to run

npx skills add https://github.com/PurpleAILAB/Vigilo --skill input-validation-purpleailab

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: input-validation
Source: https://github.com/PurpleAILAB/Vigilo/tree/main/packages/opencode/skills/input-validation
Command: npx skills add https://github.com/PurpleAILAB/Vigilo --skill input-validation-purpleailab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill identifies and mitigates common input validation vulnerabilities in smart contracts, preventing exploits that lead to fund loss and broken invariants.

Core Features & Use Cases

Vulnerability Detection: Pinpoints missing zero checks, address validation issues, array bounds errors, parameter constraints, calldata validation, and encoding problems.
Root Cause Analysis: Explains why input validation fails, such as assumption of good faith or missing bounds checking.
Use Case: An auditor can use this Skill to quickly scan a smart contract codebase for all instances where external function parameters are not adequately validated, flagging potential risks before deployment.

Quick Start

Analyze the provided smart contract code for input validation vulnerabilities.

Frequently Asked Questions about input-validation

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

FAQPage Schema

How do I detect input validation vulnerabilities in Solidity smart contracts?▼

Detect input validation vulnerabilities in Solidity by performing static analysis to identify missing zero checks, array bounds mismatches, and untrusted calldata. This process flags insecure function parameter handling and external calls before deployment.

What are common smart contract input validation risks mapped to OWASP SC04:2025?▼

OWASP SC04:2025 smart contract input validation risks include missing zero checks, address validation issues, array bounds errors, parameter constraints, calldata validation, and encoding problems. These flaws occur when contracts assume good faith or lack bounds checking.

How do I audit smart contract code for missing zero checks and array bounds errors?▼

Audit smart contract code for missing zero checks and array bounds errors by scanning the codebase to pinpoint insecure function parameter handling. Static analysis identifies exactly where external parameters are not adequately validated.

Can I analyze untrusted calldata and external calls for insecure parameter handling?▼

Yes, you can analyze untrusted calldata and external calls by applying static analysis to the Solidity code. This identifies insecure function parameter handling and provides detection patterns for mitigating these vulnerabilities.

What is the best way to mitigate web3 security flaws from unvalidated function parameters?▼

Mitigate web3 security flaws from unvalidated function parameters by applying targeted detection patterns and constraints. Root cause analysis explains why validation fails, enabling strategies to secure external calls and prevent broken invariants.

Why does smart contract input validation fail during external function calls?▼

Smart contract input validation fails during external function calls due to assumptions of good faith and missing bounds checking. Failing to validate untrusted calldata and encoding problems leads to exploits and fund loss.