โ† Back to Scanner

@penpot/mcp Security Audit Report

๐Ÿ”ญ Continuously monitored by ClawSecure Watchtower
Source:
SHA-256:

@penpot/mcp is an AI agent skill, created by penpot and published at penpot/penpot. ClawSecure audited @penpot/mcp across 72 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 65/100 (Moderate). The 4 findings concentrate in Code Injection and Permissions Manifest, including Potentially dangerous code pattern detected: base64.*decode and Potentially dangerous code pattern detected: exec\(. 3 were rated high or critical severity.

Is @penpot/mcp safe?

ClawSecure audited @penpot/mcp and assigned a security score of 65/100 (Moderate), identifying 4 findings across Code Injection and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in @penpot/mcp?

ClawSecure identified 4 findings in @penpot/mcp, concentrated in Code Injection and Permissions Manifest. 3 were rated high or critical severity. The most severe include Potentially dangerous code pattern detected: base64.*decode and Potentially dangerous code pattern detected: exec\(.

How was @penpot/mcp audited?

ClawSecure ran @penpot/mcp through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 72 files from penpot/penpot.

What does a score of 65 mean?

ClawSecure assigned @penpot/mcp a security score of 65/100, placing it in the Moderate range. This reflects 4 findings led by Code Injection that warrant review before production use. ClawSecure derives this score with a weighted deduction model (critical -20, high -10, medium -5, low -2 from a base of 100).

Audit Findings for @penpot/mcp

ClawSecure detected 4 security findings in @penpot/mcp, spanning Code Injection and Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for @penpot/mcp

Eliminate dynamic code execution
@penpot/mcp evaluates code at runtime (for example eval or dynamic exec). Remove dynamic evaluation of untrusted input, and where code generation is unavoidable, sandbox it and validate every input.
Add a config.json permissions manifest
A config.json file declares what an agent component can access: file system, network, shell execution and more. Without it, users have no visibility into what the component can do before installing. This is the single most impactful security improvement for any AI agent skill.
Pin dependencies to exact versions
Unpinned dependencies allow supply-chain attacks where a compromised version is pulled in automatically. Use exact version numbers in package.json (for example 1.2.3 instead of ^1.2.3) to keep unauthorized code out of your dependency tree. ClawSecure checks every dependency against known CVE databases.

Related Security Research

Why Generic Scanners Fail at AI Agent Securityโ†’Beyond Static Scans: Why ClawSecure Verifies Agentic Intentโ†’How to Secure an MCP Server: The 2026 Guideโ†’

Related AI Agent Security Audits

gitlab-cli-skillsScore 55/100thepopebotScore 51/100@fazaboa/opencode-auto-continueScore 55/100xlsxScore 63/100docxScore 68/100

Scanned on October 29, 2026. @penpot/mcp is one of thousands of agents audited by ClawSecure from the community-curated awesome-openclaw-skills list and the openclaw/skills repository.

Start Your Free Scan