RenderMark

• Outcome: Pass
• Latest audit: May 29, 2026 at 8:16 PM UTC
• Version:
  0.1.8

Overview

RenderMark is a coherent markdown rendering and publishing skill, but users should be careful with publishing, sharing, and saved API keys.

Install this only if you want an agent to render, publish, share, and manage markdown documents through RenderMark and optional providers. Before publishing or syncing, confirm the content is safe to send outside your machine, verify recipients and visibility, and protect any keys stored in ~/.rendermark/config.json.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code
• Excessive Agency: Unrestricted Tool Access, Autonomous Decision Making, Scope Creep

Findings (7)

Missing User Warnings

Medium

• Confidence: 94% confidence
• Finding: The skill instructs the agent to publish documents and share them externally, but it does not require an explicit user warning or confirmation that content will be transmitted to rendermark.app or shared with other recipients. In an agent setting, this can cause accidental disclosure of sensitive markdown, internal notes, or metadata when the user may have intended only local rendering or export.

Missing User Warnings

Low

• Confidence: 84% confidence
• Finding: The skill describes export behavior as returning a file path and confirming it was saved, but it does not clearly warn that the operation writes files to local disk. This can lead to unintended persistence of sensitive content on shared machines, synced folders, or monitored workspaces.

Missing User Warnings

Medium

• Confidence: 92% confidence
• Finding: The guide instructs users to place long-lived API and OAuth secrets in a local config file and shows raw secret fields, but it does not warn that these credentials are sensitive, should not be committed to source control, and should be protected with strict file permissions. In an MCP/agent context, local config files are common exfiltration targets and may be readable by other tools, logs, backups, or accidental uploads, increasing the chance of credential compromise.

Missing User Warnings

Low

• Confidence: 78% confidence
• Finding: The setup guide tells users to run a browser-based authentication flow but gives no notice that authentication will open an external browser session and may transmit account data or tokens to the RenderMark service or identity provider. While this is standard behavior, the lack of a privacy/data-sharing notice can mislead users in security-sensitive environments and reduce informed consent around what data leaves the local machine.

Missing User Warnings

Medium

• Confidence: 95% confidence
• Finding: The reference documents publishing and sharing features that send markdown content to external services, but it does not warn that user-provided document contents may leave the local environment and become accessible through third-party platforms or shareable links. In an agent setting, this omission is security-relevant because users may assume a rendering/export tool is local-only and unintentionally disclose sensitive content.

Missing User Warnings

Low

• Confidence: 88% confidence
• Finding: The export tools write files to disk, but the documentation does not clearly warn users that these operations create or overwrite local files at a chosen or default path. In an agent-driven workflow, unclear write behavior can lead to unintended persistence of sensitive documents or accidental writes to unsafe locations.

Missing User Warnings

Medium

• Confidence: 96% confidence
• Finding: The setup flow states that an API key is automatically saved to ~/.rendermark/config.json, but it does not warn about local credential storage or associated risks such as file permission exposure, backups, or multi-user systems. This is dangerous because users may unknowingly persist long-lived secrets on disk without understanding how they are protected.

VirusTotal

65/65 vendors flagged this skill as clean.