ClawHub
Back to skill

Security audit

Codeup

Security checks for vulnerabilities and agentic risk

Overview

This Codeup skill appears purpose-built for repository management, but it gives an agent live authority to delete branches/files, approve or merge code, and remove source branches without clear safety gates.

Use this only if you want an agent operating on live Codeup repositories. Prefer a least-privilege token, start with read-only access when possible, and require explicit human approval before deleting branches or files, approving/rejecting reviews, closing MRs, merging MRs, or removing source branches.

SkillSpector

Vulnerability Patterns
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • 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 (3)

Missing User Warnings

Medium
Confidence
88% confidence
Finding
The skill exposes destructive branch operations such as branch deletion without any warning, safeguard, or confirmation guidance. In a repository-management context, this increases the chance an agent or user will perform irreversible or disruptive actions that can delete work or break development workflows.

Missing User Warnings

Medium
Confidence
90% confidence
Finding
The documentation presents file creation, update, and deletion commands as routine operations without highlighting that they modify repository contents and may overwrite or remove tracked files. In an agent setting, missing cautions can lead to unintended commits or content loss, especially when parameters are constructed from user input or inferred context.

Missing User Warnings

High
Confidence
94% confidence
Finding
The merge_change_request example includes merging code and removing the source branch without any warning about irreversible repository state changes. Because merges can promote unreviewed code and source-branch removal can discard a recovery path, this is especially risky in an autonomous or semi-autonomous agent workflow.

Static analysis

No suspicious patterns detected.