security-audit

Audits code and infrastructure for security and compliance risks.

66|3|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/lgbarn/shipyard --skill security-audit-lgbarn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-audit
Source: https://github.com/lgbarn/shipyard/tree/main/skills/security-audit
Command: npx skills add https://github.com/lgbarn/shipyard --skill security-audit-lgbarn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams identify and remediate security gaps across code, infrastructure-as-code, configurations, and dependencies before release, reducing risk and audit time.

Core Features & Use Cases

  • OWASP Top 10 checks across code, configurations, and IaC to catch common security flaws early.
  • Secrets detection to identify hard-coded credentials and exposure across repositories.
  • Dependency security & license compliance scans to surface vulnerable libraries and license risks.
  • IaC hardening & container security guidance to enforce secure configurations and deployment practices.
  • Use Case: A development team runs security-audit on a multi-repo project to produce a consolidated risk report for remediation planning.

Quick Start

Run the security-audit at the root of your repository to initiate the checks and generate a findings report.

Frequently Asked Questions about security-audit

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

FAQPage Schema
How do I audit my codebase for OWASP Top 10 vulnerabilities and hard-coded secrets?

To audit your codebase for OWASP Top 10 vulnerabilities and hard-coded secrets, run a security audit at your repository root to scan code, configurations, and IaC, generating a consolidated risk findings report for remediation.

What is the best way to check dependency vulnerabilities and license compliance across multiple repositories?

Checking dependency vulnerabilities and license compliance across multiple repositories involves scanning software supply chains to surface vulnerable libraries and license risks, producing a consolidated report for remediation planning.

How do I harden infrastructure-as-code and Docker images before deployment?

To harden infrastructure-as-code and Docker images before deployment, apply security audits to enforce secure configurations and deployment practices across IaC files and container configurations, reducing risk prior to release.

Can I use a security audit to check CI/CD pipelines and software supply chains?

Yes, you can use a security audit to check CI/CD pipelines and software supply chains, extending coverage to dependencies, configuration files, and deployment practices to identify security gaps and compliance issues before release.

Does security-audit work with infrastructure-as-code files and Docker configurations?

Yes, security-audit works with infrastructure-as-code files and Docker configurations, applying IaC hardening and container security guidance to enforce secure configurations across your infrastructure and deployment setup.

What limitations should I expect when scanning multi-repo projects for security posture?

When scanning multi-repo projects for security posture, expect that the audit focuses on identifying and remediating security gaps across code, IaC, and dependencies to reduce audit time, but requires manual execution at the repository root.