Back to skill

Security audit

Git Hooks Manager

Security checks for vulnerabilities and agentic risk

Overview

This appears to be a Git hook management skill, but it can install executable Git hooks from imported JSON, which creates persistent code execution in a repository.

Install only if you intentionally want this skill to create and manage Git hooks. Review any imported hook configuration before use, because those hooks can run commands automatically during future Git operations. Prefer trusted configs, pin dependencies, and remove unwanted hooks from .git/hooks if you no longer need them.

Vulnerability Patterns
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (5)

Missing User Warnings

Medium
Confidence
95% confidence
Finding
`import_config` reads hook script contents from a JSON file and installs them directly into `.git/hooks`, making them executable on Unix via `install()`. Because Git hooks execute automatically during developer workflows, importing an untrusted config can silently establish persistent arbitrary code execution in the local repository context.

Unpinned Dependencies

Low
Category
Supply Chain
Content
click>=8.0.0
colorama>=0.4.6
pytest>=7.0.0
Confidence
93% confidence
Finding
The dependency specification for click is unpinned and allows installation of any future version at or above 8.0.0. This increases supply-chain and stability risk because builds are not reproducible and may silently pick up a compromised or breaking release.

Unpinned Dependencies

Low
Category
Supply Chain
Content
click>=8.0.0
colorama>=0.4.6
pytest>=7.0.0
Confidence
93% confidence
Finding
The dependency specification for colorama is unpinned and permits any later version at or above 0.4.6. This can expose consumers to unintended updates, including vulnerable or malicious package releases, and reduces build reproducibility.

Unpinned Dependencies

Low
Category
Supply Chain
Content
click>=8.0.0
colorama>=0.4.6
pytest>=7.0.0
Confidence
95% confidence
Finding
The dependency specification for pytest is unpinned and allows any version newer than 7.0.0 to be installed. This is risky because it can pull in vulnerable or untested releases, which is especially relevant here given a separate advisory is flagged for pytest.

Known Vulnerable Dependency: pytest — 1 advisory(ies): CVE-2025-71176 (pytest has vulnerable tmpdir handling)

Low
Category
Supply Chain
Confidence
72% confidence
Finding
The file includes pytest without constraining it away from a version affected by the cited tmpdir-handling advisory. If the vulnerable version is installed and the package is used in testing workflows that process attacker-controlled paths or files, it could introduce filesystem-related security issues.

Static analysis

No suspicious patterns detected.