arib-check-deps

Audit project dependencies for security vulnerabilities, license compliance, and supply chain risks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill mitigates supply chain risks by identifying security vulnerabilities, license compliance issues, and malicious patterns in project dependencies before they impact production.

Core Features & Use Cases

  • Vulnerability Scanning: Detects CVEs across multiple ecosystems including npm, pip, and Go.
  • License Compliance: Flags restrictive licenses like GPL or AGPL that may pose legal risks to commercial projects.
  • Supply Chain Hardening: Identifies dangerous patterns like typosquatting, suspicious post-install scripts, and unmaintained packages.

Quick Start

Run the arib-check-deps skill to perform a full security audit and dependency health check on the current project.

Frequently Asked Questions about arib-check-deps

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

FAQPage Schema
How do I audit project dependencies for security vulnerabilities?

To audit project dependencies for security vulnerabilities, run the skill to perform a full security audit and dependency health check on the current project. It detects CVEs across multiple ecosystems including npm, pip, and Go.

What is dependency supply chain hardening and how does it detect malicious packages?

Dependency supply chain hardening identifies dangerous patterns like typosquatting, suspicious post-install scripts, and unmaintained packages. It mitigates supply chain risks by finding malicious patterns in project dependencies before they impact production.

How do I check license compliance for npm, pip, and Go dependencies?

To check license compliance for npm, pip, and Go dependencies, run a full audit to flag restrictive licenses like GPL or AGPL. This identifies legal risks to commercial projects before deployment.

Can I use automated dependency scanning for continuous monitoring across diverse package ecosystems?

Yes, you can use automated dependency scanning for continuous monitoring across diverse package ecosystems. It satisfies requirements for secure deployment gates and continuous dependency monitoring throughout the software development lifecycle.

Does dependency vulnerability scanning work with both npm and Go modules?

Yes, dependency vulnerability scanning works with npm and Go modules. It detects CVEs and identifies dangerous supply chain attack vectors across multiple diverse package ecosystems including npm, pip, and Go.