Token导航 LogoToken导航

Agent Skill · 效率

dependency-auditor(依赖性审计员)

用于辅助安全审计、权限检查、凭据风险、认证流程和常见漏洞排查。它适合让 Agent 梳理敏感配置、检查依赖风险、分析鉴权逻辑或生成安全复核清单。使用时不能把工具输出直接当最终结论,涉及密钥、令牌、用户数据或生产系统时,应先确认最小权限、脱敏方式和操作边界。

dependency-auditor 是效率类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为需要联网;许可证为 MIT-0,第三方扫描已通过,按安装量在效率类的 21,003 个 Skill 里排第 2,286。

总安装 26,754周安装 1,126GitHub Stars 公开资料未说明下载 9,368核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
2.1.1

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:dependency-auditor(依赖性审计员)
来源仓库:https://github.com/alirezarezvani/dependency-auditor
安装命令:
openclaw skills install dependency-auditor
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install dependency-auditor

这个 Skill 是做什么的

效率类 Skill 把重复的整理、汇总、转换工作交给助手完成,减少手工复制粘贴。

依赖审计器用于识别第三方库安全风险与认证流程漏洞。适合安全审查、凭据管理和常见漏洞排查等合规需求场景。能生成风险清单与修复建议,但不替代人工最终判断。处理密钥或用户数据时必须限制最小权限并脱敏处理。不得将工具输出直接作为生产环境决策依据。

dependency-auditor 属于效率类 Skill,可作为该场景下的辅助能力补充。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install dependency-auditor;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

dependency-auditor 怎么安装?

在终端执行 openclaw skills install dependency-auditor。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

dependency-auditor 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

dependency-auditor 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

dependency-auditor 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

dependency-auditor 用的人多吗?

公开数据是累计安装 26,754 次,近一周安装 1,126 次,下载 9,368 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

dependency-auditor 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理效率类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

效率类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
github

GitHub 代码协作 · OpenClaw

7,632,918545需要联网MIT-0通过
nano-pdf

Nano PDF 文档 · OpenClaw

4,249,476231需要联网MIT-0通过
auto-updater

自动更新程序 · OpenClaw

2,964,063386操作浏览器MIT-0通过
video-frames

视频帧 · OpenClaw

2,621,304112需要联网MIT-0通过
gemini

Gemini 助手 · OpenClaw

2,547,39648需要联网MIT-0有提醒
dependency-auditor

依赖性审计员 · 本页

26,754—需要联网MIT-0通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
dependency-auditor
description
Dependency Auditor

Dependency Auditor

Skill Type: POWERFUL Category: Engineering Domain: Dependency Management & Security

Overview

The Dependency Auditor is a comprehensive toolkit for analyzing, auditing, and managing dependencies across multi-language software projects. This skill provides deep visibility into your project's dependency ecosystem, enabling teams to identify vulnerabilities, ensure license compliance, optimize dependency trees, and plan safe upgrades.

In modern software development, dependencies form complex webs that can introduce significant security, legal, and maintenance risks. A single project might have hundreds of direct and transitive dependencies, each potentially introducing vulnerabilities, license conflicts, or maintenance burden. This skill addresses these challenges through automated analysis and actionable recommendations.

Core Capabilities

1. Vulnerability Scanning & CVE Matching

Comprehensive Security Analysis

  • Scans dependencies against built-in vulnerability databases
  • Matches Common Vulnerabilities and Exposures (CVE) patterns
  • Identifies known security issues across multiple ecosystems
  • Analyzes transitive dependency vulnerabilities
  • Provides CVSS scores and exploit assessments
  • Tracks vulnerability disclosure timelines
  • Maps vulnerabilities to dependency paths

Multi-Language Support

  • JavaScript/Node.js: package.json, package-lock.json, yarn.lock
  • Python: requirements.txt, pyproject.toml, Pipfile.lock, poetry.lock
  • Go: go.mod, go.sum
  • Rust: Cargo.toml, Cargo.lock
  • Ruby: Gemfile, Gemfile.lock
  • Java/Maven: pom.xml, gradle.lockfile
  • PHP: composer.json, composer.lock
  • C#/.NET: packages.config, project.assets.json

2. License Compliance & Legal Risk Assessment

License Classification System

  • Permissive Licenses: MIT, Apache 2.0, BSD (2-clause, 3-clause), ISC
  • Copyleft (Strong): GPL (v2, v3), AGPL (v3)
  • Copyleft (Weak): LGPL (v2.1, v3), MPL (v2.0)
  • Proprietary: Commercial, custom, or restrictive licenses
  • Dual Licensed: Multi-license scenarios and compatibility
  • Unknown/Ambiguous: Missing or unclear licensing

Conflict Detection

  • Identifies incompatible license combinations
  • Warns about GPL contamination in permissive projects
  • Analyzes license inheritance through dependency chains
  • Provides compliance recommendations for distribution
  • Generates legal risk matrices for decision-making

3. Outdated Dependency Detection

Version Analysis

  • Identifies dependencies with available updates
  • Categorizes updates by severity (patch, minor, major)
  • Detects pinned versions that may be outdated
  • Analyzes semantic versioning patterns
  • Identifies floating version specifiers
  • Tracks release frequencies and maintenance status

Maintenance Status Assessment

  • Identifies abandoned or unmaintained packages
  • Analyzes commit frequency and contributor activity
  • Tracks last release dates and security patch availability
  • Identifies packages with known end-of-life dates
  • Assesses upstream maintenance quality

4. Dependency Bloat Analysis

Unused Dependency Detection

  • Identifies dependencies that aren't actually imported/used
  • Analyzes import statements and usage patterns
  • Detects redundant dependencies with overlapping functionality
  • Identifies oversized packages for simple use cases
  • Maps actual vs. declared dependency usage

Redundancy Analysis

  • Identifies multiple packages providing similar functionality
  • Detects version conflicts in transitive dependencies
  • Analyzes bundle size impact of dependencies
  • Identifies opportunities for dependency consolidation
  • Maps dependency overlap and duplication

5. Upgrade Path Planning & Breaking Change Risk

Semantic Versioning Analysis

  • Analyzes semver patterns to predict breaking changes
  • Identifies safe upgrade paths (patch/minor versions)
  • Flags major version updates requiring attention
  • Tracks breaking changes across dependency updates
  • Provides rollback strategies for failed upgrades

Risk Assessment Matrix

  • Low Risk: Patch updates, security fixes
  • Medium Risk: Minor updates with new features
  • High Risk: Major version updates, API changes
  • Critical Risk: Dependencies with known breaking changes

Upgrade Prioritization

  • Security patches: Highest priority
  • Bug fixes: High priority
  • Feature updates: Medium priority
  • Major rewrites: Planned priority
  • Deprecated features: Immediate attention

6. Supply Chain Security

Dependency Provenance

  • Verifies package signatures and checksums
  • Analyzes package download sources and mirrors
  • Identifies suspicious or compromised packages
  • Tracks package ownership changes and maintainer shifts
  • Detects typosquatting and malicious packages

Transitive Risk Analysis

  • Maps complete dependency trees
  • Identifies high-risk transitive dependencies
  • Analyzes dependency depth and complexity
  • Tracks influence of indirect dependencies
  • Provides supply chain risk scoring

7. Lockfile Analysis & Deterministic Builds

Lockfile Validation

  • Ensures lockfiles are up-to-date with manifests
  • Validates integrity hashes and version consistency
  • Identifies drift between environments
  • Analyzes lockfile conflicts and resolution strategies
  • Ensures deterministic, reproducible builds

Environment Consistency

  • Compares dependencies across environments (dev/staging/prod)
  • Identifies version mismatches between team members
  • Validates CI/CD environment consistency
  • Tracks dependency resolution differences

Technical Architecture

Scanner Engine (dep_scanner.py)

  • Multi-format parser supporting 8+ package ecosystems
  • Built-in vulnerability database with 500+ CVE patterns
  • Transitive dependency resolution from lockfiles
  • JSON and human-readable output formats
  • Configurable scanning depth and exclusion patterns

License Analyzer (license_checker.py)

  • License detection from package metadata and files
  • Compatibility matrix with 20+ license types
  • Conflict detection engine with remediation suggestions
  • Risk scoring based on distribution and usage context
  • Export capabilities for legal review

Upgrade Planner (upgrade_planner.py)

  • Semantic version analysis with breaking change prediction
  • Dependency ordering based on risk and interdependence
  • Migration checklists with testing recommendations
  • Rollback procedures for failed upgrades
  • Timeline estimation for upgrade cycles

Use Cases & Applications

Security Teams

  • Vulnerability Management: Continuous scanning for security issues
  • Incident Response: Rapid assessment of vulnerable dependencies
  • Supply Chain Monitoring: Tracking third-party security posture
  • Compliance Reporting: Automated security compliance documentation

Legal & Compliance Teams

  • License Auditing: Comprehensive license compliance verification
  • Risk Assessment: Legal risk analysis for software distribution
  • Due Diligence: Dependency licensing for M&A activities
  • Policy Enforcement: Automated license policy compliance

Development Teams

  • Dependency Hygiene: Regular cleanup of unused dependencies
  • Upgrade Planning: Strategic dependency update scheduling
  • Performance Optimization: Bundle size optimization through dep analysis
  • Technical Debt: Identifying and prioritizing dependency technical debt

DevOps & Platform Teams

  • Build Optimization: Faster builds through dependency optimization
  • Security Automation: Automated vulnerability scanning in CI/CD
  • Environment Consistency: Ensuring consistent dependencies across environments
  • Release Management: Dependency-aware release planning

Integration Patterns

CI/CD Pipeline Integration

# Security gate in CI
python dep_scanner.py /project --format json --fail-on-high
python license_checker.py /project --policy strict --format json

Scheduled Audits

# Weekly dependency audit
./audit_dependencies.sh > weekly_report.html
python upgrade_planner.py deps.json --timeline 30days

Development Workflow

# Pre-commit dependency check
python dep_scanner.py . --quick-scan
python license_checker.py . --warn-conflicts

Advanced Features

Custom Vulnerability Databases

  • Support for internal/proprietary vulnerability feeds
  • Custom CVE pattern definitions
  • Organization-specific risk scoring
  • Integration with enterprise security tools

Policy-Based Scanning

  • Configurable license policies by project type
  • Custom risk thresholds and escalation rules
  • Automated policy enforcement and notifications
  • Exception management for approved violations

Reporting & Dashboards

  • Executive summaries for management
  • Technical reports for development teams
  • Trend analysis and dependency health metrics
  • Integration with project management tools

Multi-Project Analysis

  • Portfolio-level dependency analysis
  • Shared dependency impact analysis
  • Organization-wide license compliance
  • Cross-project vulnerability propagation

Best Practices

Scanning Frequency

  • Security Scans: Daily or on every commit
  • License Audits: Weekly or monthly
  • Upgrade Planning: Monthly or quarterly
  • Full Dependency Audit: Quarterly

Risk Management

  1. Prioritize Security: Address high/critical CVEs immediately
  2. License First: Ensure compliance before functionality
  3. Gradual Updates: Incremental dependency updates
  4. Test Thoroughly: Comprehensive testing after updates
  5. Monitor Continuously: Automated monitoring and alerting

Team Workflows

  1. Security Champions: Designate dependency security owners
  2. Review Process: Mandatory review for new dependencies
  3. Update Cycles: Regular, scheduled dependency updates
  4. Documentation: Maintain dependency rationale and decisions
  5. Training: Regular team education on dependency security

Metrics & KPIs

Security Metrics

  • Mean Time to Patch (MTTP) for vulnerabilities
  • Number of high/critical vulnerabilities
  • Percentage of dependencies with known vulnerabilities
  • Security debt accumulation rate

Compliance Metrics

  • License compliance percentage
  • Number of license conflicts
  • Time to resolve compliance issues
  • Policy violation frequency

Maintenance Metrics

  • Percentage of up-to-date dependencies
  • Average dependency age
  • Number of abandoned dependencies
  • Upgrade success rate

Efficiency Metrics

  • Bundle size reduction percentage
  • Unused dependency elimination rate
  • Build time improvement
  • Developer productivity impact

Troubleshooting Guide

Common Issues

  1. False Positives: Tuning vulnerability detection sensitivity
  2. License Ambiguity: Resolving unclear or multiple licenses
  3. Breaking Changes: Managing major version upgrades
  4. Performance Impact: Optimizing scanning for large codebases

Resolution Strategies

  • Whitelist false positives with documentation
  • Contact maintainers for license clarification
  • Implement feature flags for risky upgrades
  • Use incremental scanning for large projects

Future Enhancements

Planned Features

  • Machine learning for vulnerability prediction
  • Automated dependency update pull requests
  • Integration with container image scanning
  • Real-time dependency monitoring dashboards
  • Natural language policy definition

Ecosystem Expansion

  • Additional language support (Swift, Kotlin, Dart)
  • Container and infrastructure dependencies
  • Development tool and build system dependencies
  • Cloud service and SaaS dependency tracking

Quick Start

# Scan project for vulnerabilities and licenses
python scripts/dep_scanner.py /path/to/project

# Check license compliance
python scripts/license_checker.py /path/to/project --policy strict

# Plan dependency upgrades
python scripts/upgrade_planner.py deps.json --risk-threshold medium

For detailed usage instructions, see README.md.


*This skill provides comprehensive dependency management capabilities essential for maintaining secure, compliant, and efficient software projects. Regular use helps teams stay ahead of security threats, maintain legal compliance, and optimize their dependency ecosystems.*

平台分布

OpenClaw

83.14%
按下载量换算7,789

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills