security-audit

Audit code and dependencies for security vulnerabilities with remediation guidance.

Updated Jan 8, 2026
One-click install
npx skills add https://github.com/cpa03/blueprintify --skill security-audit-cpa03
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-audit
Source: https://github.com/cpa03/blueprintify/tree/main/.opencode/skill/security-audit
Command: npx skills add https://github.com/cpa03/blueprintify --skill security-audit-cpa03

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits code and dependencies to identify and remediate security vulnerabilities, reducing risk from insecure libraries and unsafe code paths.

Core Features & Use Cases

  • Automated security audits across codebases and package dependencies (e.g., npm, yarn) to surface known vulnerabilities and insecure transitive dependencies.
  • Secret scanning, credential leakage checks, and review of authentication/authorization logic in changed files.
  • Use Case: Integrate into CI to generate a concise findings report and remediation guidance for developers.

Quick Start

Run the security-audit workflow on your repository to produce a findings report and remediation steps.

Frequently Asked Questions about security-audit

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

FAQPage Schema
How do I run a security audit on my code and dependencies?

To perform a security audit, execute the workflow on your repository to analyze code and dependencies. It enforces npm audit, secret scanning, and auth logic review on changed files, generating a findings report with remediation guidance.

What does secret scanning check for during a dependency audit?

Secret scanning checks for credential leakage and exposed secrets in changed files. During a dependency audit, it also reviews authentication and authorization logic to identify insecure code paths and reduce risk from leaked credentials.

Can I use this security audit for multi-language projects?

Yes, you can use this security audit for multi-language projects. It is applicable during code reviews, dependency updates, and release cycles, analyzing changed files across various languages to identify vulnerabilities and insecure libraries.

How do I fix vulnerabilities found in npm audit results?

To fix vulnerabilities found in npm audit results, follow the generated findings report. It provides remediation guidance for developers, detailing steps to update insecure libraries and resolve unsafe code paths or transitive dependencies.

When should I run a code and dependency security audit?

You should run a security audit during code reviews, dependency updates, and release cycles. Integrating it into CI ensures continuous scanning of changed files for known vulnerabilities, secret leakage, and insecure authentication logic before deployment.