Security audit
feishu-omni-todo
Security checks for vulnerabilities and agentic risk
Overview
The skill mostly does what it claims (manages todos and integrates with Feishu) but the shipped code expects Feishu credentials, external tools, and creates a persistent cron job — none of which are declared in the metadata; review before installing.
This skill's code mostly matches its description, but there are important mismatches and persistence behaviors you should consider before installing: - Credentials: The code reads FEISHU_APP_ID and FEISHU_APP_SECRET from the environment but the skill metadata does not declare these. Only supply these credentials if you trust the source and understand tenant-level Feishu access. - Hard-coded IDs & CLI calls: The code contains a hard-coded USER_ID and calls an 'openclaw' CLI to send messages; ensure these will target the correct account and that the CLI is safe and intended. - Background job: setup_cron.py will add a cron job that runs every minute to send reminders. Installing/running this will give the skill persistent background execution — consider running the reminder script manually first or reviewing the cron change before applying it. - Dependencies: The scripts require Python packages (requests, dateparser, python-crontab) not declared in metadata; install them from trusted sources and inspect the code before running. - Data storage: Todos and reminder logs are stored under ~/.openclaw/workspace; review and backup any sensitive data before use. Recommendations: do not run setup_cron.py or provide FEISHU_APP_ID/FEISHU_APP_SECRET until you (1) verify the skill source, (2) review and if necessary modify hard-coded USER_ID and message-sending logic to use your configured webhook/API, and (3) run the scripts in a restricted/test environment first. If you cannot verify the author or are uncomfortable with cron or tenant credentials, treat this skill as untrusted.
Static analysis
No suspicious patterns detected.
