Skills/npm/polotno

polotno@4.21.0

VERIFIED· install only

Publisher claims: "Design editor SDK: embed a Canva-like editor, generate designs from templates and data, export PNG, PDF, and video in the browser or on a server." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher polotno-project · publishing for 2415 daysInstalls 231KLast detonated 15 min ago
$claude mcp add polotno -- npx -y polotno
WatchReport an issue

Coverage

Bundled scripts ran with no arguments; no agent task scenario for this bundle.
Tested
8 of 48 bundled scripts run with no arguments (the rest were not run: per-bundle cap), with decoy credentials in the environment · every file read, file written and host contacted by what ran
Not tested
use of the skill by an agent

What changed since 4.20.1

vet-skills diff polotno 4.20.1 4.21.0

In the sandbox, this version reached for nothing 4.20.1 did not. Compared from the two recorded runs, not from source.

The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; bundled scripts ran with no arguments; no agent task scenario for this bundle) on 2026-11-17 and scored it 93/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 1 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.0sprocessbundled script run in the sandbox with no arguments
0.1sprocessexited 1: Node.js v22.23.5
0.1sprocessbundled script run in the sandbox with no arguments
0.3sprocessexited 1: Node.js v22.23.5
0.3sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.3sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.4sprocessexited 1: Node.js v22.23.5
0.4sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.5sprocessexited 1: Node.js v22.23.5
0.5sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.6sprocessexited 1: Node.js v22.23.5
0.6sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.7sprocessexited 1: Node.js v22.23.5
0.7sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.8sprocessexited 1: Node.js v22.23.5
0.8sprocess8 of 48 bundled scripts run with no arguments (the rest were not run: per-bundle cap)
0.8sprocessscript backend runs setup only
0.8sprocessscript backend runs setup only
0.8sprocessno install scripts to re-run

Static findings

MEDIUM
File type combined with upload actionutils/file.js:1 · File type combined with upload action — agent may exfiltrate local data files….result),t.onerror=e=>i(e)})}export const MEDIA_ACCEPT="image/*,video/*,audio/*,.json,.lottie";const e={svg:"svg",gif:"gif",lottie:"lottie",png:"image",jpg:"image",jpeg:"image",webp:"image",avif:"image",bmp:"image",heic:"image",mp4:"video"…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.
AST07

No other findings across 2,256 lines in 81 files.

Cost to the agent

Instructions loaded
≈60 tok
1 file · 81 in bundle

Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.

Known vulnerabilities

Not checked against OSV yet; the weekly check has not reached this version.