raccoon-audit

Audit codebases for secrets, vulnerabilities, dead code, and insecure patterns.

5|Updated Nov 22, 2025
One-click install
npx skills add https://github.com/AutumnsGrove/Lattice --skill raccoon-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: raccoon-audit
Source: https://github.com/AutumnsGrove/Lattice/tree/main/.claude/skills/raccoon-audit
Command: npx skills add https://github.com/AutumnsGrove/Lattice --skill raccoon-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill meticulously inspects codebases for security vulnerabilities, exposed secrets, and unnecessary clutter, ensuring a clean and secure state before deployment or release.

Core Features & Use Cases

  • Secret Detection: Identifies hardcoded API keys, passwords, and tokens.
  • Vulnerability Scanning: Checks dependencies for known security flaws.
  • Code Sanitization: Removes dead code, debug flags, and insecure patterns.
  • Git History Cleaning: Purges sensitive information from commit history.
  • Use Case: Before open-sourcing a project, use this Skill to ensure no internal credentials or sensitive information is accidentally exposed in the code or its history.

Quick Start

Run a full security audit on the current project to find and fix any issues.

Frequently Asked Questions about raccoon-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scan my codebase for exposed secrets and hardcoded credentials?

A codebase security audit identifies exposed credentials by rummaging for hardcoded API keys, passwords, and tokens. It checks for insecure coding practices and dependency flaws to ensure a clean state before deployment or open-source release.

What's the best way to remove sensitive data from git history before open-sourcing a project?

Removing sensitive data from git history involves purging exposed credentials and secrets from commit logs. A comprehensive security audit sanitizes code and verifies a clean state to prevent accidental information leakage when sharing repositories publicly.

Can this security audit detect known vulnerabilities in my project dependencies?

Yes, vulnerability scanning checks project dependencies for known security flaws. The audit addresses dependency risks alongside dead code and debug flags, ensuring insecure patterns are sanitized before you proceed with deployment.

How do I sanitize code and remove insecure coding patterns before deployment?

Code sanitization removes dead code, debug flags, and insecure coding patterns from the codebase. Conducting a pre-deployment security audit verifies that all sensitive data is purged and the project maintains a secure, clean state.

Do I need any external dependencies to perform a comprehensive codebase security audit?

No external dependencies are required to perform a comprehensive security audit. The Skill autonomously handles secret detection, vulnerability scanning, code sanitization, and git history cleaning using its internal scripts and reference components.

Why should I use an automated security audit for post-incident codebase cleanup?

An automated security audit handles post-incident cleanup by meticulously inspecting code, purging sensitive data from history, and verifying a clean state. It addresses exposed credentials and insecure patterns to restore project integrity.