render-deploy

Fail

Audited by Snyk on Aug 1, 2026

Risk Level: CRITICAL
Full Analysis

HIGH W007: Insecure credential handling detected in skill instructions.

  • Insecure credential handling detected (high risk: 0.90). The skill instructs adding an "Authorization: Bearer <YOUR_API_KEY>" header to the MCP config and shows an example export RENDER_API_KEY="rnd_xxxxx", which implies the agent or config must include user API keys verbatim (exposing secrets in prompts/outputs/config snippets), creating an exfiltration risk.

CRITICAL E005: Suspicious download URL detected in skill instructions.

  • Suspicious download URL detected (high risk: 0.80). The list contains a direct raw GitHub link to an install.sh script (curl ... | sh) which is a high-risk download pattern because executing a remote shell script can install malware if the source or contents are untrusted or tampered with.

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

  • Third-party content exposure detected (medium risk: 0.30). The skill’s runtime workflow ingests outsider-authored free text from the user’s Git repository by analyzing the codebase (e.g., reading files like package.json, requirements.txt, etc.) to generate render.yaml and determine build/start/env vars, meaning attacker-controlled repository content is processed before any item selection.

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

Issues (4)

W007
HIGH

Insecure credential handling detected in skill instructions.

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
Aug 1, 2026, 11:04 AM
Issues
4
Security Audit — snyk — render-deploy