Security audit

notify-hub

Security checks for vulnerabilities and agentic risk

Overview

The skill's code and instructions mostly match the described notification-aggregator purpose, but there are small inconsistencies and runtime behaviors (undeclared dependency on mail-cli, fallback to npx which can fetch code at runtime, and an instruction to ignore installer output) that warrant caution before installing.

This skill appears to do what it claims (route urgent SaaS emails to your primary account and make a daily digest) but please check these points before installing: - mail-cli dependency: The skill requires a configured mail-cli (npm package) with access to your mailbox; the skill metadata does not declare this. Ensure you understand and trust the mail-cli package and the account/API key it uses, because the script will read and send emails using those credentials. - Dry-run and testing: Test both router.js and summarize.js with --dry-run to confirm rule matching and output before enabling any cron jobs. - Review rules: Default rules forward messages that match keywords; review and edit ~/.config/notify-hub/config.json to avoid unintentionally forwarding sensitive emails. - npx fallback: If mail-cli is not installed locally, the scripts will use 'npx mail-cli', which can download and execute a package at runtime. If you prefer, install mail-cli yourself (npm install -g @clawemail/mail-cli) and verify its behavior before running the skill. - Odd installer instruction: The README instructs you to "ignore" any installer prompts that mail-cli may print; be cautious — confirm manually that mail-cli has created the expected profile rather than blindly ignoring prompts. If you need higher assurance, ask the owner for an explicit dependency declaration and an install script (or install mail-cli yourself from the upstream project) and review mail-cli's source and required permissions before giving it access to your mailbox.

Static analysis

Detected: suspicious.dangerous_exec

Shell command execution detected (child_process).

Critical

Code: suspicious.dangerous_exec
Location: scripts/config.js:109

Shell command execution detected (child_process).

Critical

Code: suspicious.dangerous_exec
Location: scripts/router.js:51

Shell command execution detected (child_process).

Critical

Code: suspicious.dangerous_exec
Location: scripts/summarize.js:50