buzzshield

To scan crypto agent configurations, you can run a security check that identifies exposed private keys, API keys, and mnemonics in files like CLAUDE.md and .env. This process uses rule-based checks to detect credential leaks and reduce deployment risk.

Smart contract risk remediation detects common vulnerability signals like reentrancy guards, unchecked external calls, and ownership misuse. Automated checks apply heuristics to your codebase to find these risk patterns and provide graded reports with actionable remediation steps.

Checking wallet safety involves flagging risky transaction patterns such as missing approval gates, unbounded transfers, and drain-like flows. Security scanning tools identify these on-chain operational risks in your codebase to prevent dangerous wallet configuration mistakes.

Yes, you can generate CI/CD-friendly security reports in terminal, JSON, or markdown formats. Running a security scan with a markdown report flag produces graded output with remediation steps suitable for integration into continuous integration pipelines.

Agent configuration security review identifies unsafe agent flags, overly broad tool access, missing trust gates, and misconfigured cron handlers. It checks these governance and feature-flag problems to ensure secure agent definitions before production deployment.

You should run a security scan during pre-production reviews, after configuration changes, or when adding MCP servers and API keys. Periodic security hygiene scanning ensures ongoing protection against accidental leaks and dangerous wallet configuration mistakes.