Peekaboo

The materials state that no keys or environment variables are required. No API tokens, account credentials, or long-lived secrets are requested or stored, so credential exposure appears low.

The description says it supports visual question answering via local or remote AI models. Although no fixed remote endpoint is listed in the checks, screenshots or screen contents may be sent to a configured model service when a remote model is used. No unknown or unrelated exfiltration endpoint is identified, so this is a caution rather than high risk.

The system checks explicitly mark executes-code, and as a macOS CLI/optional MCP server it will run local processes and invoke screenshot-related system capabilities. This is inherent to this type of tool, and the provided materials do not show requests for system privileges beyond its stated purpose.

Its core function is capturing screenshots of applications or the entire system, so it can access sensitive information visible on-screen. Based on the current materials, there is no indication of additional file-system write/read access, database access, or overbroad permissions unrelated to its function.

The source is a public GitHub repository, open source and auditable, under the MIT license, with relatively strong community adoption (~4.7k stars). These are strong risk-reducing signals. Maintenance status is unknown, which adds some uncertainty, but not enough on its own to raise this to high risk.