Scan .NET applications for security weaknesses and generate severity-rated findings.
npx skills add https://github.com/shahdanish/vibepos --skill security-scan-shahdanish
Please help me install this Agent Skill. Skill: security-scan Source: https://github.com/shahdanish/vibepos/tree/main/skills/security-scan Command: npx skills add https://github.com/shahdanish/vibepos --skill security-scan-shahdanish
It helps you proactively uncover security weaknesses in .NET applications by scanning dependencies, source code patterns, configuration, and data-protection practices—so you can remediate issues before release.
Run the security scan skill with the instruction phrase "security scan" to generate a severity-rated report with OWASP mappings and concrete remediation steps.
High-intent search queries and answers about installing and using this skill.
Scanning .NET applications for OWASP vulnerabilities involves checking source code patterns, NuGet dependencies, and configuration for injection, deserialization, and XSS issues. This skill produces a severity-rated report mapping findings to OWASP categories with specific remediation patterns.
To detect hardcoded secrets in .NET configuration files, scan source and config types for high and medium-confidence credentials. This skill identifies risky secrets and provides guidance to move them to user secrets or environment and managed key stores.
Yes, you can check NuGet dependencies for known CVEs before release. This skill scans direct and transitive NuGet packages for known CVEs, providing severity mapping and upgrade guidance to remediate vulnerable packages.
Validating CORS policy and authentication configuration in ASP.NET involves reviewing settings for overly broad origins and missing explicit auth. This skill checks your auth and CORS configuration, flagging insecure settings for remediation.
The best way to find insecure data protection and PII logging in .NET is to scan for risky logging of sensitive data and missing encryption strategies. This skill identifies insecure handling of PII and flags missing data-protection practices.
You should run a security scan on your .NET codebase during pre-release security gates, after dependency updates, for quarterly security reviews, or when preparing for security audits. This proactive approach catches vulnerabilities before release.
BasharAmsoAudit code and dependencies for security vulnerabilities and generate a severity-rated report.
cwinvestmentsScan project dependencies for vulnerabilities, outdated packages, and supply chain risks.
spallempatiIntegrate SAST tools into CI/CD to block pull requests with high-severity findings.
zangxin75Conduct security audits and code vulnerability reviews with SAST scans.
