ClawHub
Back to skill

Security audit

GitHub Contribution

Security checks across malware telemetry and agentic risk

Overview

The skill appears to help with GitHub contribution workflows, but it includes destructive Git cleanup and force-push steps without enough guardrails.

Review the Git commands before use. Run this only in a clean, backed-up worktree or disposable clone, avoid repos with uncommitted work, and confirm any force-push targets your own PR branch. Prefer safer variants such as dry-run clean checks and `--force-with-lease`.

SkillSpector

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

Missing User Warnings

Medium
Confidence
94% confidence
Finding
The documented sync script includes destructive commands (`git reset --hard` and `git clean -fdx`) that can permanently delete local commits and untracked files. In a contribution skill, users are likely to copy-paste these commands, so the lack of an explicit data-loss warning materially increases the chance of accidental destructive execution.

Missing User Warnings

Medium
Confidence
92% confidence
Finding
The skill instructs `git push -f` without warning that force-pushing rewrites remote history and can overwrite collaborators' work. Because this is framed as a standard rebase workflow, users may execute it routinely without validating branch ownership or whether others depend on the branch.

Missing User Warnings

Low
Confidence
84% confidence
Finding
The troubleshooting section recommends branch deletion with `git branch -D` but does not warn that deleting the wrong local branch is irreversible if it contains unpushed work. This is less severe than reset/clean or force-push, but still a real destructive-operation safety issue in instructional content.

Missing User Warnings

Medium
Confidence
96% confidence
Finding
The script performs `git reset --hard` against the upstream branch without any explicit warning or confirmation immediately beforehand. In an automation context, this can irreversibly discard local uncommitted changes in the working tree, making accidental data loss likely if the repository already contains work.

VirusTotal

63/63 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.