ClawHub
Back to skill

Security audit

CI/CD Pipeline Toolkit

Security checks across malware telemetry and agentic risk

Overview

This CI/CD helper is purpose-aligned and disclosed, but users should review generated deployment workflows before using them in real environments.

Install in a virtual environment, pin dependency versions for reproducible use, use least-privilege tokens for status checks, and manually review generated CI/CD files before committing them, especially anything that can deploy or publish from production branches.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (4)

Missing User Warnings

Medium
Confidence
91% confidence
Finding
The skill exposes a deployment_trigger action that explicitly supports production deployments but provides no warning, guardrails, approval requirements, or confirmation flow for potentially destructive changes. In a CI/CD context, triggering deployments can directly modify live systems, so omission of safety messaging and controls increases the risk of accidental or unauthorized production impact.

Unpinned Dependencies

Low
Category
Supply Chain
Content
PyYAML>=6.0
requests>=2.28.0
python-jenkins>=1.8.0
Confidence
98% confidence
Finding
The dependency is specified with a lower bound only, so installations can resolve to different future versions over time. This weakens reproducibility and can unintentionally pull in a newly introduced vulnerable or incompatible release, increasing supply-chain risk.

Unpinned Dependencies

Low
Category
Supply Chain
Content
PyYAML>=6.0
requests>=2.28.0
python-jenkins>=1.8.0
Confidence
98% confidence
Finding
The requests package is not pinned to an exact version, allowing dependency resolution to drift across environments and over time. This can introduce vulnerable or behavior-changing releases without review, which is a supply-chain and stability concern.

Unpinned Dependencies

Low
Category
Supply Chain
Content
PyYAML>=6.0
requests>=2.28.0
python-jenkins>=1.8.0
Confidence
97% confidence
Finding
Using a minimum version only for python-jenkins permits uncontrolled upgrades to any later version that satisfies the constraint. That reduces build reproducibility and can expose the skill to newly introduced vulnerabilities or breaking behavior in the CI integration path.

VirusTotal

65/65 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.