source-code-scanning

Automate source code security scanning for vulnerabilities, CVEs, and hardcoded secrets.

7|1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/ArianHobson333/claude-bug-bounty-stack --skill source-code-scanning-arianhobson333
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: source-code-scanning
Source: https://github.com/ArianHobson333/claude-bug-bounty-stack/tree/main/vendor/communitytools/projects/pentest/.claude/skills/source-code-scanning
Command: npx skills add https://github.com/ArianHobson333/claude-bug-bounty-stack --skill source-code-scanning-arianhobson333

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires semgrep, bandit, gosec, trivy, grype, brakeman, pip-audit, npm audit, govulncheck, detect-secrets, gitleaks, pip-audit, safety, dependency-check, spotbugs, findsecbugs, pmd, pharos, flawfinder, cppcheck, tfsec, checkov, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the security scanning and analysis of source code, identifying potential vulnerabilities and security risks.

Core Features & Use Cases

  • Automated Security Scanning: Performs automated static analysis for vulnerabilities (OWASP Top 10, CWE Top 25), CVEs in third-party dependencies, hardcoded secrets, malicious code, and insecure patterns.
  • Multi-Language Support: Scans code in Python, JS, Java, Go, PHP, Ruby, and more.
  • Dependency CVE Scan: Checks for known CVEs in package lockfiles/manifests.
  • Secrets Detection: Detects hardcoded credentials, tokens, and other sensitive information.
  • Manual Review Patterns: Identifies common security patterns and code snippets indicative of security vulnerabilities.

Quick Start

Run the source-code-scanning skill on the repository 'my-repo'.

Frequently Asked Questions about source-code-scanning

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

FAQPage Schema
How do I automate source code security scanning for vulnerabilities and hardcoded secrets?

To automate source code security scanning, you can run this skill on your repository to detect hardcoded secrets, insecure patterns, and vulnerabilities using static analysis and dependency checks across multiple languages like Python, JS, Java, and Go.

Does static analysis support scanning multiple programming languages like Python, Go, and Java?

Yes, static analysis supports multi-language scanning for Python, JS, Java, Go, PHP, Ruby, and more. It uses specific tools like bandit, gosec, and spotbugs to identify security vulnerabilities and insecure patterns across these codebases.

Can I use dependency scanning to check for CVEs in package lockfiles and manifests?

Yes, you can use dependency scanning to check for known CVEs in package lockfiles and manifests. The skill utilizes tools like pip-audit, npm audit, and govulncheck to identify vulnerable third-party dependencies during the analysis process.

What is the best way to detect hardcoded credentials and tokens in a repository?

The best way to detect hardcoded credentials is by using secrets detection tools like detect-secrets and gitleaks. This skill automates this process to identify hardcoded tokens, credentials, and other sensitive information within your source code.

How do I scan an infrastructure-as-code repository for insecure patterns and misconfigurations?

You can scan infrastructure-as-code repositories for insecure patterns by running this skill, which integrates tools like tfsec and checkov to identify security risks, vulnerabilities, and misconfigurations in your codebase.