arib-check-security

Audit code for OWASP Top 10 vulnerabilities and supply-chain dependency risks.

2|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/AribSudia/claude-code-methodology --skill arib-check-security
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: arib-check-security
Source: https://github.com/AribSudia/claude-code-methodology/tree/main/.claude/skills/arib-check-security
Command: npx skills add https://github.com/AribSudia/claude-code-methodology --skill arib-check-security

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the challenge of maintaining consistent application security by automating the detection of OWASP Top 10 vulnerabilities and supply-chain risks across the codebase.

Core Features & Use Cases

  • OWASP Compliance: Scans code for patterns and anti-patterns defined in the OWASP Top 10:2025 framework.
  • Supply Chain Audit: Identifies outdated dependencies, CVEs, and license compliance issues.
  • Unified Reporting: Aggregates findings from multiple agents and system hooks into a single, actionable security report.
  • Use Case: Run this before merging sensitive authentication or payment code to ensure no critical vulnerabilities are introduced into the production environment.

Quick Start

Execute the arib-check-security skill to perform a comprehensive security audit on the entire codebase.

Frequently Asked Questions about arib-check-security

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

FAQPage Schema
How do I automate OWASP Top 10 vulnerability scanning across my codebase?

Automate OWASP vulnerability scanning by running a comprehensive audit that analyzes code paths for security defects and compliance gaps defined in the OWASP Top 10:2025 framework, generating a severity-ranked report.

What is a supply-chain security audit and how does it detect dependency risks?

A supply-chain security audit identifies outdated dependencies, CVEs, and license compliance issues by scanning your project's dependency management tools. It aggregates these findings into a structured, severity-ranked vulnerability report.

Can I run a security audit on specific file paths instead of the entire repository?

Yes, the security audit operates across specific file paths or the entire repository to identify security defects. This allows you to target sensitive authentication or payment code before merging into production.

Do I need a security-auditor agent to perform a dependency vulnerability scan?

Yes, generating a unified security report requires integration with a security-auditor agent and dependency management tools. This combination aggregates code-level and supply-chain findings into a single actionable output.

What's the best way to check for CVEs and license compliance before a production merge?

Run a comprehensive security audit combining OWASP code-level analysis with supply-chain dependency scanning. This identifies CVEs, license issues, and compliance gaps, producing a severity-ranked report before merging.

What are the limitations of automated code-level security analysis?

Automated security analysis requires integration with dependency management tools and a security-auditor agent to function, meaning it cannot generate a structured severity-ranked report without these environment dependencies.