update-pepper

Fail

Audited by Snyk on Jun 19, 2026

Risk Level: CRITICAL
Full Analysis

CRITICAL E005: Suspicious download URL detected in skill instructions.

  • Suspicious download URL detected (high risk: 0.80). This is a personal GitHub repository (github.com/qwibitai/pepper.git) from an unknown user rather than an official vendor — personal/forked GitHub repos can legitimately host code but are commonly used to distribute unvetted or malicious binaries, so treat it as suspicious until you inspect the repo, verify the maintainer, check stars/forks/commits, and review any build artifacts or release assets before running anything.

MEDIUM W011: Third-party content exposure detected (indirect prompt injection risk).

  • Third-party content exposure detected (high risk: 0.95). The required workflow fetches and ingests upstream repository content at runtime via git fetch upstream --prune and then reads it into the LLM context through git log, git diff --name-only, and conflict previews (git merge --no-commit ...; git diff --name-only --diff-filter=U), where the upstream repo is an outsider-authored source.

MEDIUM W012: Unverifiable external dependency detected (runtime URL that controls agent).

  • Potentially malicious external URL detected (high risk: 1.00). The skill fetches and merges from an upstream Git repository at https://github.com/qwibitai/pepper.git during runtime (git fetch/merge/rebase/cherry-pick), so remote code and prompt/skill content from that URL can directly change/drive the agent's behavior and execution.

Issues (3)

E005
CRITICAL

Suspicious download URL detected in skill instructions.

W011
MEDIUM

Third-party content exposure detected (indirect prompt injection risk).

W012
MEDIUM

Unverifiable external dependency detected (runtime URL that controls agent).

Audit Metadata
Risk Level
CRITICAL
Analyzed
Jun 19, 2026, 11:36 PM
Issues
3
Security Audit — snyk — update-pepper