Security audit
Security checks for vulnerabilities and agentic risk
This is a documentation-only skill for using an email CLI, and its sensitive actions are expected for managing email accounts.
Install only if you intend to let the agent help operate your email account. Review recipients, message IDs, attachment paths, and delete/send commands before running them, and prefer keyring or password-manager based credential storage over plaintext config values.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
backend.auth.keyring = "imap-example"
Then run himalaya account configure <account> to store the password.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
backend.auth.keyring = "imap-example"
Then run himalaya account configure <account> to store the password.
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
himalaya account configure
Or create `~/.config/himalaya/config.toml` manually:
```toml
[accounts.personal]
The skill shows commands for composing and sending email, including template send, but does not warn users that executing them will transmit content, headers, and recipient information over SMTP and potentially to external parties. For markdown files, behaviors affecting privacy or external data transmission should be explicitly disclosed.
This markdown file describes himalaya message delete 42 as a common operation but provides no warning that it deletes user email and may affect mailbox state or retention. Under the markdown-specific missing-warning rule, destructive actions that can affect user data should be accompanied by a user-facing caution.
The attachment download section instructs users to save attachments, including to a specific directory, but does not warn that this writes files to the local filesystem and may overwrite or expose sensitive data depending on location and defaults. Markdown descriptions should disclose behaviors that affect user data or system state.
This markdown file provides concrete configuration examples that place passwords directly in config fields and later references OAuth client credentials and tokens. Although it notes that raw passwords are 'testing only, not recommended,' it does not provide an explicit broader warning that these settings expose sensitive credentials in local configuration or command output/history if handled carelessly.
The documentation shows MML attachment syntax using local filesystem paths without explicitly warning that those paths cause the referenced files to be read and sent in outbound email. In an agent or automation context, a user may copy these examples and unintentionally exfiltrate sensitive local files, especially if path values are templated or influenced by untrusted input.
No suspicious patterns detected.