Dependency Auditor

Community

borghei

dependency-auditor

Scan project dependencies for vulnerabilities, license issues, and upgrade opportunities across Python, Node.js, Go, and Rust. Use when auditing dependencies, checking licenses, planning upgrades, or assessing supply chain security.

Overview

Publisher	borghei
Repository	`Claude-Skills`
Skill name	`dependency-auditor`
Stars	856
Forks	154
Bundled files	16
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
16 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by borghei on GitHub. Read the source before you install it.

Installation

Install the Dependency Auditor AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/borghei/Claude-Skills/tree/main/engineering/dependency-auditor
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/borghei/Claude-Skills.git /tmp/Claude-Skills
mkdir -p .claude/skills
cp -r /tmp/Claude-Skills/engineering/dependency-auditor .claude/skills/dependency-auditor

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Dependency Auditor in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Dependency Auditor on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Dependency Auditor is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Dependency Auditor

A multi-language toolkit for analyzing, auditing, and managing dependencies. It scans manifests and lockfiles across 8+ ecosystems to surface vulnerabilities, classify licenses, detect bloat, and produce safe, phased upgrade plans — giving teams visibility into security, legal, and maintenance risk hidden in their dependency trees.

Core Capabilities

Vulnerability scanning & CVE matching — match direct/transitive deps against a built-in CVE database with CVSS scoring across Node, Python, Go, Rust, Ruby, Java, PHP, .NET.
License compliance — classify into permissive / weak-copyleft / strong-copyleft / proprietary / unknown tiers and detect incompatible combinations (e.g. GPL contamination).
Outdated & maintenance detection — categorize updates by patch/minor/major severity; flag abandoned or end-of-life packages.
Dependency bloat analysis — find unused, redundant, or oversized packages and consolidation opportunities.
Upgrade path planning — semver breaking-change prediction, risk matrix, prioritization, rollback strategies.
Supply chain security — provenance checks, typosquatting/malicious-package detection, transitive risk scoring.
Lockfile analysis — validate freshness, integrity hashes, and cross-environment consistency for deterministic builds.

When to Use

Auditing a project's dependencies for vulnerabilities or supply-chain risk.
Checking license compliance before distribution or M&A due diligence.
Planning safe, phased dependency upgrades.
Adding a dependency security gate to CI/CD.
Cleaning up unused or redundant dependencies.

Clarify First

Before running the audit, confirm these inputs. If any is unknown or vague, ASK — do not assume:

Project & ecosystem — the project path and which manifests/lockfiles (the input the scanner parses)
Audit focus — vulnerabilities, license compliance, or upgrade planning (selects dep_scanner.py vs license_checker.py vs upgrade_planner.py)
Policy & gate — license policy strictness and fail-on-severity threshold (sets --policy, --fail-on-high, and the CI verdict)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.

Tools

Tool	Purpose	Command
`dep_scanner.py`	Scan manifests/lockfiles across 8+ ecosystems, match CVEs, produce a security report	`python scripts/dep_scanner.py /path/to/project --format json --fail-on-high`
`license_checker.py`	Classify dependency licenses by risk tier and detect conflicts vs the project license	`python scripts/license_checker.py /path/to/project --policy strict --warn-conflicts`
`upgrade_planner.py`	Evaluate semver gaps, assess breaking-change risk, output a phased upgrade plan	`python scripts/upgrade_planner.py deps.json --risk-threshold medium --timeline 30`

References

Load the reference that matches the task — keep this file lean and pull detail on demand:

references/capabilities-and-best-practices.md — full breakdown of every analysis capability, the scanner/analyzer/planner internals, use cases by team, advanced/enterprise features, recommended scan cadences, and metrics/KPIs. Read when you need the deep capability or architecture detail.
references/tools-integration-and-troubleshooting.md — quick-start and CI/CD/scheduled-audit integration commands, complete per-tool flag/output reference, the troubleshooting table, and success-criteria targets. Read when running the tools, wiring them into pipelines, or diagnosing failures.
references/vulnerability_assessment_guide.md — how to assess, prioritize, and remediate dependency vulnerabilities (CVSS, exploitability, disclosure timelines). Read when triaging or responding to security findings.
references/license_compatibility_matrix.md — comprehensive license-type reference and compatibility matrix for combining open-source dependencies. Read when resolving license conflicts or making distribution decisions.
references/dependency_management_best_practices.md — strategic, governance, security, and operational best practices across the dependency lifecycle. Read when establishing dependency policy or team workflows.

Scope & Limitations

This skill covers:

Parsing dependency manifests and lockfiles for JavaScript/Node.js, Python, Go, Rust, Ruby, Java, PHP, and C#/.NET ecosystems.
Matching dependencies against a built-in vulnerability database of common CVE patterns with severity scoring.
Classifying licenses into risk tiers (permissive, weak copyleft, strong copyleft, proprietary, unknown) and detecting conflicts.
Generating prioritized, phased upgrade plans with breaking-change analysis, rollback procedures, and time estimates.

This skill does NOT cover:

Real-time querying of live vulnerability databases (NVD, OSV, GitHub Advisory); the built-in DB is a representative subset. For continuous monitoring, see skill-security-auditor.
Container image or OS-level package scanning. For infrastructure auditing, see ci-cd-pipeline-builder or observability-designer.
Automated PR creation for dependency updates (Dependabot/Renovate-style); the skill produces plans and reports, not code changes.
Runtime dependency analysis or dynamic import tracing; detection is static manifest/lockfile parsing only.

Integration Points

Skill	Integration	Data Flow
skill-security-auditor	Feed vulnerability scan results into broader security audit workflows	`dep_scanner.py --format json` output consumed as evidence artifacts
ci-cd-pipeline-builder	Embed dependency gates in CI/CD pipelines	`dep_scanner.py --fail-on-high` and `license_checker.py --policy strict` as pipeline steps
release-manager	Attach dependency audit reports to release checklists	JSON reports from all three tools included in release documentation
pr-review-expert	Flag dependency changes during pull request review	Scanner diff between base and head branch dependency files
env-secrets-manager	Ensure dependency tooling credentials (registry tokens) are securely managed	Registry authentication tokens stored and rotated via secrets manager
observability-designer	Monitor dependency health metrics over time	Scan summary statistics exported to monitoring dashboards

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Dependency Auditor AI skill do?

Why use Dependency Auditor on TypingMind?

Because you install it once and use it with any model. Dependency Auditor is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Dependency Auditor in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/borghei/Claude-Skills/tree/main/engineering/dependency-auditor. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Dependency Auditor?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Dependency Auditor?

As many as you like. As long as a model supports skills, you can use Dependency Auditor with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Dependency Auditor AI skill free?

It is published on GitHub by borghei. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Django Patterns

affaan-m

CommunityPopular

Patrones de arquitectura Django, diseño de API REST con DRF, buenas prácticas de ORM, caché, señales, middleware y aplicaciones Django de nivel producción.

Quarkus Patterns

Patrones de arquitectura Quarkus 3.x LTS con Camel para mensajería, diseño de API RESTful, servicios CDI, acceso a datos con Panache y procesamiento asíncrono.

Quarkus Security

Buenas prácticas de seguridad en Quarkus para autenticación, autorización, JWT/OIDC, RBAC, validación de entrada, CSRF, gestión de secretos y seguridad de dependencias.

Quarkus Verification

Bucle de verificación para proyectos Quarkus: build, análisis estático, pruebas con cobertura, escaneos de seguridad, compilación nativa y revisión de diff antes del lanzamiento o PR.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Dependency Auditor

Core Capabilities

When to Use

Clarify First

Tools

References

Scope & Limitations

Integration Points

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now