ClawHub
Back to skill

Security audit

upgrade-deps

Security checks for vulnerabilities and agentic risk

Overview

This skill gives an agent a structured dependency-upgrade workflow with disclosed repository edits, tests, lockfile regeneration, and reporting safeguards.

Install this if you want an agent to actively upgrade dependencies in a repository. Expect it to run package-manager commands, read release notes online, edit manifests and lockfiles, run tests/builds, and potentially create commits; for ambiguous requests, specify whether you want analysis only, security-only fixes, one package, or all dependencies.

SkillSpector

Vulnerability Patterns
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (2)

Vague Triggers

Medium
Confidence
94% confidence
Finding
The skill advertises very broad trigger phrases such as 'update packages', 'fix the npm audit', and 'is it safe to upgrade', which can match common user requests and cause the skill to activate in contexts where the user did not intend a dependency-modification workflow. Because this skill is empowered to inspect manifests, change dependencies, regenerate lockfiles, and run tests/builds, unintended invocation can lead to unnecessary code changes, wasted compute, or disruptive package updates beyond the user’s actual goal.

Vague Triggers

Medium
Confidence
90% confidence
Finding
The 'When to use this skill' section repeats expansive activation conditions, including handling Dependabot/Renovate PRs and audit warnings, without sufficiently constraining scope or requiring explicit user confirmation. This increases the chance of the agent entering a high-impact maintenance workflow automatically, even when the user may only want analysis, triage, or a narrower fix, creating a pathway for unintended repository modifications.

Static analysis

No suspicious patterns detected.