dapp-lint

Scanning your dApp frontend for Web3 anti-patterns and BigInt safety violations involves running the dapp-lint skill, which utilizes oxlint or eslint to automatically detect unsafe coercions, wei handling errors, and address checksum failures, providing detailed reports.

Automated code quality checks detect common Web3 frontend bugs such as unsafe BigInt coercions, wei handling errors, address checksum failures, timestamp confusion, hardcoded chain IDs, and unsafe number coercions that threaten application reliability.

Yes, this linting skill works with both oxlint and eslint. It integrates these linters to perform comprehensive automated code analysis and flag high-impact Web3 anti-patterns within your dApp frontend project.

To check your dApp code for address checksum failures and wei handling errors before deployment, execute a Web3 anti-pattern scan to automatically identify and flag these critical issues, ensuring better security and financial reliability.

The best way to prevent unsafe number coercions in Web3 frontend code is to run an automated linter scan that specifically targets BigInt safety violations and unsafe coercions, generating detailed reports on identified vulnerabilities.

You should use a dedicated Web3 linter instead of standard code quality tools when your dApp frontend handles BigInt operations, wei conversions, or address comparisons, as standard linters cannot detect these specific Web3 anti-patterns.