email-to-calendar
Audited by Socket on Nov 22, 2026
3 alerts found:
Securityx2AnomalyThe workflow is broadly aligned with its stated email-to-calendar purpose and does not show confirmed data theft or malicious instructions. However, the optional third-party gogcli fork/branch install followed by credentialed account operations is a significant supply-chain and credential-forwarding concern.
This module is an event-tracking utility that stores records in a local JSON file and can validate them against calendar search results. Its orphan-cleanup path passes command-line and JSON-derived values into a shell command using shell=True without safe argument handling, creating a command-injection risk when validation detects an orphan and script_dir is set. No hardcoded credentials, suspicious network destinations, or clear evidence of intentional malware appear in this fragment; severity is a security warning requiring remediation.
This script searches calendar events and compares dates and title keywords, but interpolates the untrusted TIME argument into Python source without escaping, enabling arbitrary Python execution as the invoking user. Non-ISO DATE also reaches that source through the external date parser, whose output safety cannot be confirmed from this file. No specific malicious payload, domain, or credential access is present; this is a high-severity code-injection vulnerability, not evidence of intentional malware.