dependency-audit

Identifies CVEs and outdated npm dependencies across all services via npm audit in JSON mode.

Updated Feb 21, 2026
One-click install
npx skills add https://github.com/abzhaw/juliaz_agents --skill dependency-audit-abzhaw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dependency-audit
Source: https://github.com/abzhaw/juliaz_agents/tree/main/meta/agents/security-agent/skills/04-dependency-audit
Command: npx skills add https://github.com/abzhaw/juliaz_agents --skill dependency-audit-abzhaw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates security auditing of npm dependencies across multiple services to identify known CVEs and outdated packages.

Core Features & Use Cases

  • Cross-service npm audit to surface vulnerabilities across orchestrator, bridge, frontend, cowork-mcp, and backend.
  • Reports CVEs with severity levels, differentiates direct vs transitive dependencies, and flags packages older than 2 years.
  • Suitable for CI/CD pipelines and periodic security reviews to prioritize remediation.

Quick Start

Run an audit across all services to generate a consolidated vulnerability report and start remediation.

Frequently Asked Questions about dependency-audit

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

FAQPage Schema
How do I audit npm dependencies for vulnerabilities across multiple microservices?

You can audit npm dependencies for vulnerabilities across multiple microservices by running a cross-service npm audit in JSON mode to generate a consolidated vulnerability report with severity levels.

What is the difference between direct and transitive dependency vulnerabilities in npm audit?

Direct dependency vulnerabilities originate from packages explicitly listed in package.json, while transitive vulnerabilities stem from nested sub-dependencies automatically installed by those direct packages.

Can I run an npm security audit in a CI/CD pipeline?

Yes, you can run an npm security audit in CI/CD pipelines to automate periodic security reviews, surface known CVEs across services, and prioritize remediation during development workflows.

How do I identify outdated npm packages that are older than two years?

You can identify outdated npm packages older than two years by running an automated dependency audit that flags packages based on their age to help prioritize security updates and remediation.

Does npm audit report severity levels for known CVEs?

Yes, npm audit reports severity levels for known CVEs, allowing you to differentiate between critical, high, moderate, and low vulnerabilities across direct and transitive dependencies.

What's the best way to consolidate vulnerability reports across different services?

The best way to consolidate vulnerability reports across different services is running an automated cross-service npm audit that aggregates known CVEs and outdated packages into a single unified report.