AGENT SKILL

dependency-auditor

Audit and manage dependencies across multi-language projects. Identifies vulnerabilities, license conflicts, transitive dependency risks, and safe-upgrade paths. Use when auditing third-party packages before release, investigating a CVE, planning a major version bump, or running a license-compliance review.

License 许可
MIT
最近更新
2026-07-14
Stars
★ 0
Forks
0

01 前言 Front Matter

name
dependency-auditor
description
Audit and manage dependencies across multi-language projects. Identifies vulnerabilities, license conflicts, transitive dependency risks, and safe-upgrade paths. Use when auditing third-party packages before release, investigating a CVE, planning a major version bump, or running a license-compliance review.

02 资源文件 15

03 SKILL.md 正文

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.

04 同仓库更多 Skills

aneeba-pixel
aneeba-pixel/claude-skills

syllabus

Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Triggers whenever a user uploads a syllabus, course outline, or curriculum document and wants supplementary readings. Also triggers on: 'syllabus reading list', 'find papers for my course', 'create a reading list from this syllabus', 'recent research for my class', 'supplementary readings', 'find journal articles for these topics', 'what recent papers cover this material', 'any new research on these course topics', 'update my syllabus with recent papers'. Even casual mentions when a syllabus is attached should trigger this skill.

★ 0
aneeba-pixel
aneeba-pixel/claude-skills

research

Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends/sentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Triggers — "research [topic]", "look into [topic]", "what do we know about [topic]", "investigate [topic]", "find me information on [topic]", "do some research on [topic]", "I need to understand [topic]", or any research request that doesn't obviously match a more-specific specialist skill. Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.

★ 0
aneeba-pixel
aneeba-pixel/claude-skills

pulse

Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X/Twitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend/sentiment/problems/opportunities/comparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Triggers: 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]', or any variation requesting multi-source recency intelligence on a topic. Also use for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.

★ 0
aneeba-pixel
aneeba-pixel/claude-skills

patent

Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search / freedom-to-operate / competitive landscape / acquisition diligence / litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Triggers: 'prior art search for [invention]', 'patent search on [topic]', 'freedom to operate analysis', 'FTO for [product]', 'patent landscape for [field]', 'is [invention] novel', 'patents on [topic]', 'competitive patent analysis', 'prior art for litigation', 'patent diligence on [company]'. Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.

★ 0
aneeba-pixel
aneeba-pixel/claude-skills

notebooklm

Browser automation skill for controlling Google's NotebookLM. Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio Overview, infographics, slide decks, study guides, briefing docs, mind maps, timelines, FAQs), and creating new notebooks. Triggers on any phrase involving NotebookLM — 'open NotebookLM', 'check my [name] notebook', 'pull info from NotebookLM', 'ask my notebook about X', 'add [source] to NotebookLM', 'create an infographic in NotebookLM', 'use NotebookLM Studio', 'generate a slide deck from my notebook', or any variation where the goal involves NotebookLM. Requires browser automation environment — fails gracefully when unavailable.

★ 0
aneeba-pixel
aneeba-pixel/claude-skills

litreview

Academic literature orientation skill that searches papers via Consensus, builds a strategic search plan using PICO (default) or SPIDER / Decomposition / hybrid as fallbacks, and synthesizes findings into a professionally formatted Word document (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5/10/20 queries) controls coverage vs. speed. Output is a 'launching pad' — not a finished review, but an orientation guide that lets a researcher dive in confidently. Triggers: 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'. Do NOT trigger for single one-off paper searches where the user just wants a quick list — that's a plain Consensus search.

★ 0