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 & dependenciesno flags
Code that runs when you install it, before you ever call a tool.
Runs code / shell commands2 findings
INFOtests/test_process_manager_macos.py:31 — Code-execution call site (subprocess spawn) in TEST code. Down-weighted to informational: this is the test exercising the server, not the server's runtime surface.
INFOtests/test_process_manager_macos.py:142 — Code-execution call site (subprocess spawn) in TEST code. Down-weighted to informational: this is the test exercising the server, not the server's runtime surface.
Secrets & credentials1 finding
HIGHtests/test_process_manager.py:130 — A secret-shaped env var appears on the same line as a log/print sink: a credential may be written to logs or stdout, where it can leak.
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.