Travelmapify

Create interactive travel route maps from location names with real FlyAI hotel search. Supports AI Vision analysis of travel planning images.

What to consider before installing: 1) Command injection risk: scripts/amap-proxy.js builds shell commands that interpolate user-provided query/city values into a child_process exec string. If you will expose this proxy to any untrusted input or use untrusted images/text, this is a real risk. Ask the author to sanitize/escape inputs or switch to child_process.spawn with argument arrays. 2) Embedded API key & undeclared env use: the package and docs ship a default Amap API key and the code will use AMAP_KEY if present. The skill claims no required credentials but relies on AMAP_KEY, OPENCLAW_WORKSPACE and the FlyAI CLI. Prefer to supply your own Amap key via environment variable and confirm the included key is legitimate and allowed for reuse. 3) Dependency on sibling skill and local servers: the proxy calls into a relative ../amap-maps script. Installing this skill without a trusted amap-maps implementation could execute arbitrary code. Only install if you have the expected amap-maps skill from a trusted source. 4) Run in a sandbox first: test in an isolated environment (VM/container) and review the omitted scripts (hotel-search-server.py, ensure_servers_running.py, etc.) before enabling on your main system. 5) If you need this functionality but want lower risk: request the author to (a) remove embedded API keys, (b) declare required env vars and permissions, (c) avoid shell interpolation of user inputs, and (d) document exact runtime network endpoints. If the author provides that follow-up and fixes the command-exec patterns, this assessment could change to benign.

Type: OpenClaw Skill Name: travelmapify Version: 2.2.2 The skill bundle contains a critical shell injection vulnerability in 'scripts/amap-proxy.js', where user-controlled query and city parameters are passed unsanitized to 'child_process.exec'. Additionally, 'scripts/ensure_servers_running.py' implements aggressive server management by force-killing any existing processes on ports 8769 and 8780 using 'lsof' and 'os.kill'. While these behaviors are documented as part of the skill's automatic server management and geocoding functionality, the lack of input validation and the invasive process handling pose significant security risks.