dependency-triage

Featured

Scan package manifests and lockfiles for outdated packages and known CVEs. Groups updates by risk (patch, minor, major). Use in dependency sweeper loops.

AI & Automation 9,472 stars 1298 forks Updated today MIT

Install

View on GitHub

Quality Score: 94/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
49
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Dependency Triage Skill ## Output per package ```markdown ### package-name (ecosystem: npm|pip|go|etc.) - Current: x.y.z - Suggested: x.y.z - Risk: patch | minor | major - CVE: none | CVE-XXXX (severity) - Actionable: yes | no (denylist / human gate) - Suggested loop action: patch-in-worktree | escalate-human | skip ``` ## Classification Rules - **patch**: semver patch or lockfile-only security fix with no API change - **minor**: semver minor — cautious, verifier required - **major**: always escalate-human unless explicitly pre-approved in state - **denylist**: packages in state denylist → escalate-human, no auto-touch - **high-severity CVE**: escalate if fix requires major or breaking change ## Rules - Prefer the smallest safe bump that resolves the advisory. - Never bundle unrelated package updates in one change. - Record human overrides from `dependency-sweeper-state.md` every run. - If lockfile conflict or peer dependency warning → escalate-human.

Details

Author
cobusgreyling
Repository
cobusgreyling/loop-engineering
Created
1 months ago
Last Updated
today
Language
JavaScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category