# Dependency Audit

Decide whether to add, keep, or remove a dependency.

- Repository: https://github.com/Archive228/loopkit (756 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-07-14
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add Archive228/loopkit --skill dependency-audit -g -a claude-code -y`
Codex: `npx skills add Archive228/loopkit --skill dependency-audit -g -a codex -y`
Cursor: `npx skills add Archive228/loopkit --skill dependency-audit -g -a cursor -y`
Gemini CLI: `npx skills add Archive228/loopkit --skill dependency-audit -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add Archive228/loopkit`

## Description

Decide whether to add, keep, or remove a dependency. Use before adding any package.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Dependency Audit
Before adding a package, ask:
1. **Can the stdlib do it?** No lodash for `Array.map`. No left-pad-tier packages.
2. **Is it already in the tree?** Don't add axios if the project uses fetch.
3. **Is it alive?** Last commit, open issues, maintainer responsiveness.
4. **Cost?** A 500KB dep to format a date isn't worth it. Check the install size and transitive deps.
5. **Security?** Known CVEs? Postinstall scripts?
When you do add one, justify it in the PR body. Never silently grow package.json. For existing deps: anything unused or one-function gets removed.