Skills/ClawHub/imap-email

imap-email@1.0.3

VERIFIED· install only

Publisher claims: "Read and manage email via IMAP (ProtonMail Bridge, Gmail, etc.). Check for new/unread messages, fetch content, search mailboxes, and mark as read/unread. Works with any IMAP server including ProtonMail Bridge." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry ClawHubPublisher mvarrieur · publishing for 281 daysInstalls 6,967Last detonated 16 h ago
$clawhub install imap-email
WatchReport an issue

Coverage

Bundled scripts ran with no arguments; no agent task scenario for this bundle.
Tested
install scripts, with decoy credentials in place · second launch with the clock 45 days ahead · 1 of 1 bundled script run with no arguments, with decoy credentials in the environment · every file read, file written and host contacted by what ran
Not tested
use of the skill by an agent

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (3 scenarios; bundled scripts ran with no arguments; no agent task scenario for this bundle) on 2026-11-19 and scored it 88/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 3 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessinstall script run in the sandbox
0.0sprocessexec /usr/bin/grep
0.0sprocessexited 1: ./setup.sh: line 11: ps: command not found
0.0sprocessbundled script run in the sandbox with no arguments
0.1sprocessexited 1: Node.js v22.23.5
0.1sprocess1 of 1 bundled script run with no arguments
0.1sprocessscript backend runs setup only
0.1sprocessscript backend runs setup only
0.1sprocesssecond launch, clock +45 days, CI unset
0.1sprocessexec /usr/bin/grep
0.1sprocessexited 1: ./setup.sh: line 11: ps: command not found

Static findings

HIGH
Access to sensitive file pathsskill.json:140 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"Always add .env to .gitignore",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssetup.sh:43 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesecho "✅ Created .env file"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsSKILL.md:44 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files3. The `.env` file is automatically ignored by gitFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsskill.json:135 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"Credential exposure if .env is committed to version control",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsskill.json:117 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"Create .env file with IMAP credentials before use"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsscripts/imap.js:10 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesrequire('dotenv').config({ path: __dirname + '/../.env' });Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsSKILL.md:58 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files**⚠️ Security:** Never commit your `.env` file! It's already in `.gitignore` to prevent accidents.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsSKILL.md:42 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files1. Copy `.env.example` to `.env` in the skill folderFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssetup.sh:29 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# Create .env fileFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsSKILL.md:196 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files- Store credentials in `.env` (add to `.gitignore`)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsskill.json:129 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"Stores credentials in .env file (add to .gitignore)",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssetup.sh:30 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filescat > .env << EOFFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05

Cost to the agent

Instructions loaded
≈1,452 tok
1 file · 7 in bundle

Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.

Known vulnerabilities

Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.