chainaudit 1.0.2

Smart contract security scanner — Slither + ML exploitability prediction

ChainAudit

Smart contract security scanner powered by Slither + ML exploitability prediction.

Web app → chainaudit.vercel.app

---

Install

pip install chainaudit

Prerequisites:

pip install slither-analyzer
pip install solc-select && solc-select install 0.8.24 && solc-select use 0.8.24

---

Usage

# Single file
chainaudit scan contract.sol

# Directory
chainaudit scan ./contracts --recursive

# Zip archive
chainaudit scan contracts.zip

# JSON output
chainaudit scan contract.sol --json

# Skip exploit simulation
chainaudit scan contract.sol --ml-only

Exit code 1 if CRITICAL vulnerabilities found — use in CI to block deployments:

chainaudit scan contracts/ --recursive || echo "Vulnerabilities found, blocking deploy"

---

GitHub Action

- uses: aizen299/smart-contract-auditor@v1
  with:
    target: contracts/
    fail-on-critical: true

---

What It Detects

EVM (Ethereum, Polygon, BNB Chain...)

Severity	Examples
CRITICAL	Reentrancy, Controlled Delegatecall
HIGH	Unchecked Token Transfer, Weak Randomness, tx.origin Auth
MEDIUM	Timestamp Dependence, Unchecked Send
LOW	Missing Zero Check, Missing Events

L2 / Arbitrum / Optimism — auto-detected

Severity	Examples
CRITICAL	Cross-Chain Replay Attack, Bridge Reentrancy
HIGH	L2 Block Number Assumption, Sequencer Dependence, Address Aliasing
MEDIUM	Force-Include Griefing, Gas Price Assumption

L2 rules activate automatically when the scanner detects Arbitrum/Optimism identifiers (ArbSys, xDomainMessageSender etc.) in the contract source.

---

ML Predictions

Each finding includes an ML-predicted exploitability score trained on the SmartBugs dataset (143 contracts, 88% accuracy).

{
  "title": "Reentrancy",
  "severity": "CRITICAL",
  "ml_exploitability": "CRITICAL",
  "ml_confidence": 0.96
}

---

Links

• GitHub: aizen299/smart-contract-auditor
• Web app: chainaudit.vercel.app
• Issues: GitHub Issues