Algorand Vulnerability Scanner checks stateful applications and smart signatures against 11 patterns from the Not So Smart Contracts database, including rekeying, close-to fields, fee checks, group size, replay protection and clear state handling.
Every scan opens with a coverage table where each pattern is marked found, clear or n/a with a reason, followed by full write-ups of each finding and a fix. It can also run the Tealer static analyzer when it is installed.
What You Get
- A coverage table with one row per pattern and a verdict of found, clear or n/a with evidence
- Findings with severity, location, vulnerable code, attack scenario and a recommended fix
- A transaction field validation checklist for payments, asset transfers, application calls and inner transactions
- Tealer commands for local use and CI, including a fail-on severity option
Common Use Cases
- Auditing a PyTeal or Beaker application before launch
- Reviewing a TEAL smart signature for fee and close-to checks
- Validating that a fix for a reported Algorand issue holds
- Training a team on Algorand-specific security patterns
What Makes It Unique
The skill never treats silence as a clean result. It requires all 11 rows in the coverage table, lists rationalizations to reject such as a clean Tealer run meaning a clean contract, and asks for the name of the field or opcode searched when a pattern is marked clear. Its patterns come from Algorand’s transaction model, and each one is tied to a Tealer detector where one exists.
Under The Hood
The skill is a markdown instruction file with a linked resource of pattern details. It tells the agent to search the project for TEAL and PyTeal files, read them, and optionally run the tealer command, which the user installs with uv tool install. Tealer runs locally on contract files and writes a JSON report if asked. The skill does not fetch web pages or call remote APIs and does not change the contract source.