travel-planner-trvl: why it is not safe to use
travel-planner-trvl passed most checks but sends default-on anonymous telemetry and pulls live web content into context, so it warns rather than clears.
What we found
Our scan gave travel-planner-trvl a warn (80/100). It is open-source Go under a noncommercial license, needs no API keys, hardcodes no secrets, runs no shell or system-mutating commands, and does not touch keychains, cookies, or credentials. Two items kept it from a clean pass.
First, it sends an anonymous daily telemetry heartbeat by default. The payload is a random local install-id plus the tool version and Go runtime, and it explicitly excludes your IP, hostname, username, search queries, and travel data. It is still on unless you opt out.
Second, like any web-scraping tool, it returns live third-party content from flight and booking sites into the assistant context. That is an inherent prompt-injection surface. We found no malicious content in the repo itself.
What to do instead
If you want to run it, disable telemetry by setting TRVL_NO_TELEMETRY, NO_TELEMETRY, or DO_NOT_TRACK. Treat any scraped travel results as untrusted input, and avoid pairing the skill with actions that can move money or send data without your review. If default-on telemetry is a dealbreaker for your setup, choose a tool with telemetry off by default.
Source: https://github.com/MikkoParkkola/trvl
We report what our security review found at the time we checked, with the goal of keeping people safe. Projects change; if a maintainer has since fixed this, we are glad to recheck it. Email hello@agentpod.com.