Iva Personal Assistant

The evidence clearly documents normal-user installation, a fail-closed Telegram allowlist, a userbot read-only switch, owner-only terminal plugin installation, inbound injection screening, outbound secret redaction, and data flows to cloud models, transcription services, and an optional private GitHub mirror; data-flow transparency therefore earns full credit. Updates use build, probe, switch, and rollback, while destructive CRM-dedup tests demonstrate backup-before-replacement, fault recovery, and symlink-escape resistance, providing strong rollback evidence. Deductions apply because the agent shell inherits the full process environment and runs with the installer's user privileges, while document bodies, userbot chats, and browser output remain unscreened. Some userbot writes are governed only by prompt instructions, and no universal per-action confirmation mechanism is shown. Dependencies are versioned and the repository claims audit remediation and supplies security-test scripts, but the supplied evidence contains no lockfile, provenance verification, or comprehensive ongoing vulnerability process. Attribution identifies smixs and project lineage, with private reporting channels, but publisher identity remains unknown.

The README, security policy, package metadata, and tests are internally consistent about the release, runtime, security boundaries, and recovery behavior. Seeded property tests, fault injection, and extensive regression cases further support self-consistency. Failure handling is unusually concrete: tool-schema fallback, reminder fallback delivery, diagnostic bundles, explicit configuration errors, and interrupted-update recovery justify full marks for failure messages. Dependency availability is supported only statically through declared Node 24, eve, cloud services, and installation requirements; the evidence does not establish a comprehensive unified fallback for outages across Telegram, model providers, Deepgram, search, and Google services.

The material identifies business owners, specialists, executives, and everyday users and supplies concrete voice, CRM, document, reminder, and search scenarios. Multiple model and search providers, optional vectors, skills, MCP, plugins, read-only operation, and custom rules offer substantial adaptation. The security policy thoroughly states sanitizer blind spots, plugin trust boundaries, cloud-API exposure, and userbot risks, earning full capability-boundary credit. Trigger precision is reduced because natural-language interpretation, skill prompts, and configuration modes govern important behavior, and userbot joins, invites, contact imports, and reactions are not wrapped by the server guardrail. Environment fit is primarily limited to Ubuntu/Debian, systemd, and Node 24 rather than broad cross-platform support.

The README has clear navigation and dedicated architecture, feature, installation, cost, documentation, release-history, and license sections, alongside English/Russian documentation, first-minute examples, FAQ, troubleshooting, and numerous use cases. Package naming, CLI naming, versions, and release notes are consistent, and the complete MIT text is supplied. Limitations—including beta userbot ban risk, sanitizer gaps, latest-release-only support, and cloud data exposure—are candidly documented, supporting full marks across most convention criteria. Maintenance responsibility receives two points because vulnerability email and private reporting, response expectations, issue/PR routes, and a support policy are present, but there is no verified organizational identity, demonstrated multi-maintainer structure, or formal long-term maintenance commitment.

Outputs are designed for Telegram-native rich messages, checklists, tables, document links, reminders, and directly inspectable Obsidian-compatible Markdown, making the static output design highly usable. Layered long-term memory, personal CRM, actionable reminders, Google Workspace integration, and a user-controlled vault provide clear marginal value beyond an ordinary chatbot. Cost disclosure covers models, VPS hosting, voice, and provider choice, but the quoted monthly amounts, savings, and end-to-end outcomes remain repository claims without independent execution or comparative evidence, so cost-benefit is not awarded full marks.

Major claims are traceable to named documentation sections, release records, package versions, the security policy, and concrete tests for frontmatter handling, recovery, and fault injection. The tests use fixed seeds and explicit recovery invariants. The sources also distinguish stated behavior, known gaps, beta risks, and marketing scenarios without presenting this static review as an executed validation, supporting strong fact/inference separation. Cross-source corroboration is reduced because all evidence is repository-authored and many central product claims appear only in the README or changelog; the supplied code excerpts do not cover the Telegram bridge, redaction gate, installer, updater, or complete end-to-end behavior.