dependency-audit
Dependency Audit
Evaluating New Dependencies
Before adding any dependency, run through this evaluation checklist. Every "no" answer is a risk that must be explicitly accepted.
Evaluation Checklist
- Maintenance: Last commit within 6 months? Issues responded to? More than one maintainer?
- Adoption: More than 1,000 weekly downloads (npm) or equivalent? Used by known projects?
- Bundle size: Checked via bundlephobia.com or equivalent? Is tree-shaking supported?
- License: Compatible with your project license? (See license matrix below)
- Security: No open CVEs? Has a security policy? Publishes signed releases?
- API surface: Does it do one thing well, or is it a kitchen-sink package?
- Alternatives: Have you checked if the standard library or an existing dep covers this?
- Transitive deps: How many transitive dependencies does it pull in?
Quick Evaluation Commands
More from claude-code-community-ireland/claude-code-resources
design-ui
This skill should be used when the user asks to "design a UI", "create a landing page", "build a dashboard", "generate a website design", "make a product page", or needs guidance on UI design patterns, accessibility standards, design tokens, or eliminating generic AI-generated design patterns (vibe-code).
12security-review
Security review checklist covering OWASP Top 10, authentication, authorization, input validation, secrets management, and common vulnerability patterns. Reference when reviewing code for security.
7design-patterns
Reference library of proven UI design patterns, component templates, and sector-specific conventions for high-quality design generation.
6architecture-decision-record
ADR format and methodology for documenting significant technical decisions with context, alternatives considered, and consequences. Use when making or documenting architectural decisions.
5pr-description
Pull request authoring standards — structured descriptions, linking issues, providing test evidence, and writing good summaries. Reference when creating or describing pull requests.
4refactoring-patterns
Safe refactoring techniques — extract method, rename, move, inline, and structural patterns. Includes code smell identification and transformation recipes. Use when refactoring code or improving structure.
4