repo-setup

Security checks across malware telemetry and agentic risk

Overview

Review before installing: this repo setup guide is coherent, but its GitHub token handling could expose a user’s account token.

Install only if you are comfortable adapting the commands. Prefer GitHub CLI login, SSH, or a credential helper instead of token-in-URL cloning; avoid storing tokens in shell profiles; do not print remotes that may contain secrets; and run dependency installs only for repositories you trust or inside an isolated environment.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • 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 (1)

Missing User Warnings

Medium
Confidence
96% confidence
Finding
The skill recommends cloning with a personal access token embedded directly in the HTTPS URL (`https://${GH_TOKEN}@github.com/...`). Tokens placed in command lines and remote URLs can be exposed through shell history, process listings, Git configuration, logs, or by being persisted as the repository's origin URL, creating a realistic credential leakage risk.

VirusTotal

64/64 vendors flagged this skill as clean.

View on VirusTotal