Dependency Safety Check

Screens third-party project dependencies for known vulnerabilities and supply-chain risk before installation using a bundled check-deps.py script. Use when user asks to install, add, update, upgrade, or pin packages with npm, pnpm, yarn, bun, pip, uv, poetry, or cargo, or when deciding whether a package version is safe to install. Do NOT use for OS package managers such as apt, brew, yum, apk, or pacman.

5 starsSecurity

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add bolasblack/claude-skills --skill dependency-safety-check
Manual install
git clone --depth 1 https://github.com/bolasblack/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/skills/dependency-safety-check ~/.claude/skills/dependency-safety-check

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Dependency Safety Check

Run a dependency security screen before installing third-party project packages.

## Critical Rules

- **Always run `scripts/check-deps.py` before installing or upgrading third-party dependencies.**
- **Use the default 30-day minimum package age unless the user or project policy explicitly chooses another value.**
- **Never set the minimum age below 7 days.**
- **Never silently skip the check because the user seems in a hurry.**
- **If the checker returns `REJECT`, do not install unless the user explicitly overrides the risk.**
- **If the checker returns `REVIEW`, summarize the warnings and ask before proceeding.**
- **If the checker cannot complete because of network/API failures, treat the install as blocked until the user chooses a manual override.**
- **For plain bootstrap installs** like `npm install`, `npm ci`, `pnpm install`, `yarn install`, `bun install`, `pip install -r requirements.txt`, `uv sync`, or `poetry install`, inspect the manifest first and screen the direct dependencies being introduced or changed in this task. If there is no diff, screen the direct dependencies from the manifest before installing.

## Workflow

### 1. Determine ecosystem and target packages

Infer the dependency ecosystem from the user request first. If that is ambiguous, inspect the project files.

Use [references/ecosystems.md](references/ecosystems.md) for command mapping, manifest detection, and package-spec normalization.
Read the full skill on GitHub

Details

Skill name
dependency-safety-check
Path
skills/dependency-safety-check/SKILL.md
Repo updated
18 November 2026

FAQ

What does the Dependency Safety Check skill do?

Screens third-party project dependencies for known vulnerabilities and supply-chain risk before installation using a bundled check-deps.py script. Use when user asks to install, add, update, upgrade, or pin packages with npm, pnpm, yarn, bun, pip, uv, poetry, or cargo, or when deciding whether a package version is safe to install. Do NOT use for OS package managers such as apt, brew, yum, apk, or pacman.

How do I install the Dependency Safety Check skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add bolasblack/claude-skills --skill dependency-safety-check. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Dependency Safety Check popular?

It lives in bolasblack/claude-skills, which has 5 GitHub stars and 0 forks.

Related skills

Browse the most popular Claude skills, all security skills, or write your own with the skills generator.