source-audit

Analyze source code for dependency, secret, and configuration security issues.

1|1|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/dapperdivers/roundtable-arsenal --skill source-audit-dapperdivers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: source-audit
Source: https://github.com/dapperdivers/roundtable-arsenal/tree/main/pentest/source-audit
Command: npx skills add https://github.com/dapperdivers/roundtable-arsenal --skill source-audit-dapperdivers

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps security teams identify common source code security weaknesses without needing to build or run an application, reducing the effort required for early vulnerability assessment.

Core Features & Use Cases

  • Dependency Vulnerability Checks: Reviews project dependencies for known vulnerable packages and suspicious dependency names.
  • Security Configuration Analysis: Examines application configuration files and Dockerfiles for insecure settings, exposed ports, missing protections, and risky practices.
  • Secrets Detection: Scans source files for exposed credentials, tokens, private keys, and sensitive connection strings during code review workflows.

Quick Start

Ask the source-audit skill to analyze a project directory for dependency risks, leaked secrets, insecure configurations, and Dockerfile security issues.

Frequently Asked Questions about source-audit

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

FAQPage Schema
How do I scan source code for security flaws without running the application?

To scan source code without execution, analyze dependencies, secrets, configurations, and Dockerfile definitions. This identifies vulnerabilities and exposed credentials early by reviewing project files directly.

How do I detect exposed secrets and credentials in my repository?

Detect exposed secrets by scanning source files for tokens, private keys, and sensitive connection strings. This identifies leaked credentials during code review workflows without needing application execution.

Can I check project dependencies for known vulnerable packages before deployment?

Yes, check project dependencies for known vulnerable packages and suspicious dependency names. This dependency analysis flags security risks during pre-deployment audits and DevSecOps workflows.

How do I find insecure settings in Dockerfiles and application configurations?

Find insecure settings by examining configuration files and Dockerfiles for exposed ports, missing protections, and risky practices. This security configuration analysis reveals implementation weaknesses.

Do I need to install external tools to perform a source code security audit?

No, you do not need external tools. The audit requires command-line script execution and uses the Python standard library to process and detect vulnerable patterns in the project directory.