Security Validation Scanner FAQs

Question 1

What types of vulnerabilities does this skill detect?

Accepted Answer

The skill scans for hardcoded secrets (like AWS keys and Stripe tokens), user-specific absolute paths, insecure SSH configurations, and the use of dangerous security flags in commands.

Question 2

Can I integrate this into my automated CI/CD pipeline?

Accepted Answer

Yes, the skill includes a shell script that can produce JSON output, allowing for programmatic parsing and integration into automated testing and deployment workflows.

Question 3

How do I fix a 'path portability' finding?

Accepted Answer

Path portability issues occur when absolute local paths (e.g., /Users/name/project) are found. The skill recommends converting these to repo-relative paths or using environment variables.

Question 4

How does the severity-based enforcement work?

Accepted Answer

Findings are categorized as CRITICAL (blocks merge), HIGH (requires fixes), or MEDIUM (requires review). CRITICAL findings must be resolved before the code can be committed or merged.

Question 5

Does it scan documentation files?

Accepted Answer

Yes, it is specifically designed to scan both source code and documentation files (like .md, .txt, and .rst) to ensure credentials aren't accidentally included in guides.

Security Validation Scanner

Key Features

Use Cases

Security Validation Scanner

Key Features

Use Cases