mayar
Audited by Snyk on Aug 9, 2026
HIGH W007: Insecure credential handling detected in skill instructions.
- Insecure credential handling detected (high risk: 1.00). The skill explicitly tells agents to request and embed API keys in commands or environment variables (e.g.,
npx -y mayar@latest api-key <your_api_key>,export MAYAR_API_KEY=<your_api_key>,--api-key <key>), which requires the LLM to output secret values verbatim and risks exfiltration.
CRITICAL E005: Suspicious download URL detected in skill instructions.
- Suspicious download URL detected (high risk: 0.70). These URLs include a direct raw link to an untrusted shell script (https://raw.githubusercontent.com/mayarid/mayar-cli/main/install.sh), which is high risk to download and execute from an unvetted source; the rest are documentation, package-registry, or repository links that appear low risk.
MEDIUM W011: Third-party content exposure detected (indirect prompt injection risk).
- Third-party content exposure detected (medium risk: 0.30). The required runtime workflow for
mayar docs/docs <topic>explicitly fetches and renders HTML documentation content at runtime from Mayar’s docs site (via the CLI’s docs command), meaning the LLM ingests outsider-authored text from that remote source without selecting a specific item first.
MEDIUM W012: Unverifiable external dependency detected (runtime URL that controls agent).
- Potentially malicious external URL detected (high risk: 0.90). The plan explicitly makes the CLI fetch and install an external SKILL.md at runtime from https://raw.githubusercontent.com/mayarid/mayar-cli/refs/heads/main/SKILL.md, which is agent instruction content that will be written into agent skill directories and therefore directly controls agent prompts/behavior.
MEDIUM W009: Direct money access capability detected (payment gateways, crypto, banking).
- Direct money access detected (high risk: 1.00). The skill documents a payments-focused CLI (Mayar) with explicit commands to create and manage payments, invoices, payment-links, QR payment channels, and account balance, and includes API-key auth. These are direct financial execution operations (e.g.,
payment create,invoice create,payment-link edit,qrcode,balance).
Issues (5)
Insecure credential handling detected in skill instructions.
Suspicious download URL detected in skill instructions.
Third-party content exposure detected (indirect prompt injection risk).
Unverifiable external dependency detected (runtime URL that controls agent).
Direct money access capability detected (payment gateways, crypto, banking).