Dangerous exec
- Finding
- Shell command execution detected (child_process).
Security checks across static analysis, malware telemetry, and agentic risk
The skill is mostly a Godot project generator, but it writes local files from free-form names and runs a shell command in a way that needs review before use.
Use this only in a dedicated Godot project/workspace, review generated files before committing or running them, avoid path-like names such as ../ in commands, and be cautious with the open command until it uses safer process execution.
VirusTotal findings are pending for this skill version.
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If an agent or user supplies a name containing path traversal such as ../, the tool could write outside the expected project folder or overwrite files without a confirmation step.
The CLI writes generated files using the provided name directly. Similar project/scene/component generation paths are shown, with no visible check that the resolved path remains inside the intended Godot project directory.
fs.writeFileSync(path.join(scriptsDir, name + '.gd'), content);
Restrict generated names to safe filenames, resolve and verify paths stay inside the project directory, and prompt before overwriting existing files.
Running the open command executes whatever godot binary is found on PATH, and unusual directory names containing shell metacharacters could affect the command.
The skill runs a shell command to launch Godot and concatenates the current working directory into the command string instead of using a non-shell API with separated arguments.
execSync('godot --path "' + PROJECT_DIR + '"', { stdio: 'inherit' });Use execFile/spawn with argument arrays, escape or validate paths, declare Godot as an expected dependency, and avoid running the open command from untrusted or oddly named directories.
Users have less provenance information to verify the package and may not realize it will invoke a local Godot binary for the open command.
The package has no source/homepage provenance listed, and the metadata declares only node even though the documented open workflow and code rely on a local Godot executable.
Source: unknown; Homepage: none; Required binaries (all must exist): node
Install only if you trust the published package, verify the local code, and ensure the intended Godot executable is first on PATH.