Security flags foundOur static scan found signals worth reviewing before you trust this with an agent. See exactly what, per check, below.
Telemetry disclosureNone detected.No undisclosed network egress turned up in static checks. That is not proof the tool sends nothing once it runs.
Security tierTier 1, Contained.No network access and no credentials. Runs entirely on its own. What tiers mean Install-time hooks & dependencies1 finding
HIGHpackage.json — npm 'prepare' lifecycle hook: install hook runs an opaque or unrecognized command at install time, before any code review: the arbitrary-code-on-install supply-chain vector.
Runs code / shell commandsno flags
Whether the server can execute commands on your machine.
Secrets & credentials2 findings
INFOsrc/index.test.ts:19 — Reads a secret-shaped environment variable. Ordinary for a credentialed server; recorded for completeness.
INFOsrc/index.ts:18 — Reads a secret-shaped environment variable. Ordinary for a credentialed server; recorded for completeness.
Network calls outno flags
Hardcoded endpoints it reaches beyond what it documents.
Prompt-injection passthroughno flags
Whether it pipes untrusted external content back as agent instructions.
Permission scope breadthno flags
How much access it asks for versus what its job needs.
How to read this: these are static checks over the source at a point in time. They catch the patterns above, not everything. Absence of a flag is not absence of danger, and a tool that runs cleanly can still behave differently once installed. We do not call any tool simply "safe". Runtime-behavior checks are the next layer we are adding.