Skills web3-testing Audit History
📦

Audit History

web3-testing - 4 audits

Audit version 4

Latest Safe

Jan 17, 2026, 08:45 AM

Documentation-only skill containing code examples and best practices for smart contract testing. Static findings are false positives triggered by blockchain testing terminology (prank, fork, deal), environment variable references demonstrating secure secret handling patterns, and markdown code block syntax. The skill teaches recommended security practices and has no executable code, network calls, or file access capabilities.

2
Files scanned
595
Lines analyzed
1
findings
claude
Audited by
No security issues found

Risk Factors

🔑 Env variables (1)

Audit version 3

Safe

Jan 17, 2026, 08:45 AM

Documentation-only skill containing code examples and best practices for smart contract testing. Static findings are false positives triggered by blockchain testing terminology (prank, fork, deal), environment variable references demonstrating secure secret handling patterns, and markdown code block syntax. The skill teaches recommended security practices and has no executable code, network calls, or file access capabilities.

2
Files scanned
595
Lines analyzed
1
findings
claude
Audited by
No security issues found

Risk Factors

🔑 Env variables (1)

Audit version 2

Safe

Jan 5, 2026, 05:10 PM

This is a prompt-based documentation skill containing only guidance, examples, and best practices for smart contract testing. The skill has no executable code and does not access files, networks, or execute commands. References to environment variables in example configurations are standard patterns for user projects.

4
Files scanned
521
Lines analyzed
1
findings
claude
Audited by
No security issues found

Risk Factors

Audit version 1

Safe

Jan 5, 2026, 05:10 PM

This is a prompt-based documentation skill containing only guidance, examples, and best practices for smart contract testing. The skill has no executable code and does not access files, networks, or execute commands. References to environment variables in example configurations are standard patterns for user projects.

4
Files scanned
521
Lines analyzed
1
findings
claude
Audited by
No security issues found

Risk Factors