Analyzed 24 days ago · 2 anonymous rescans remaining · register free to re-analyze any time.
Public analysis · read only
Register free to re-analyze

shrimqy/Sefirah

2,731 58 132 issues
C#
GPL-3.0

Project Overview

anthropic / claude-opus-4-7

Sefirah

Windows desktop app that syncs clipboard, notifications, files, SMS, calls and media with Android devices.

AI Verdict
Clean— AI Trust Assessment

True Intent (AI Assessment)

A legitimate open-source Windows client for phone-to-PC synchronization, paired with a companion Android app.

README Accuracy

Accurate

Notes

README features (clipboard, notifications, SMS, calls, media, file transfer, scrcpy mirroring, storage integration) map directly to interfaces and modules in the source (IClipboardFeature, ICallFeature, IScreenMirrorService, etc.).

What Is This?

Sefirah is a Windows (with limited Linux support) desktop application built with WinUI/Uno that acts as a companion to a separate Android app (Sefirah-Android), providing bidirectional device integration similar to KDE Connect or Microsoft's Phone Link. The codebase is a substantial C# application (~1MB source) organized around a feature/service architecture with dependency injection via CommunityToolkit.Mvvm and Microsoft.Extensions.Hosting.

The problem it solves is fragmented cross-device workflows: users who want clipboard sync, notification mirroring, file transfer, SMS/call handling, media control, and screen mirroring between their phone and PC without relying on proprietary vendor-locked solutions (Samsung/Microsoft ecosystems). It positions itself as an open-source alternative for Windows users on any Android device.

Target users are Windows 11 / Windows 10 desktop users with Android phones who want deep phone integration. They install the Windows app (Microsoft Store or sideload) plus the Android companion (Play Store / IzzyOnDroid), pair the two over the same LAN (ports 5149-5169) using a key-verification flow, and then interact through system tray, notifications, and dedicated UI panes.

Architecturally, the app uses SQLite (via a DatabaseContext with migration support) to persist paired devices, contacts, conversations, messages, call logs, notifications, and remote apps. Networking uses mDNS discovery, TCP sockets, and optional Bluetooth pairing. Feature modules (IClipboardFeature, INotificationFeature, IMediaFeature, ICallFeature, IFileTransferService, IScreenMirrorService using scrcpy, IAdbService, etc.) are wired through interfaces in Data/Contracts. UI is XAML-based with view models, dialogs for pairing/connection requests, and an onboarding flow.

No red flags observed: GPL-3.0 licensed, active repo (2.7k stars), transparent feature set matching README, published on Microsoft Store, and includes a privacy policy. Complexity is appropriate for the scope; no obvious telemetry or suspicious network endpoints visible in the sampled code.

Your Report, Tab by Tab
At a Glance
2,731Stars
58Forks
132Open Issues
July 2025Last Active
Desktop App (Windows companion)C#GPL-3.0
Technology Stack
LanguagesC#, XAML
Runtime.NET 8+ (WinUI 3 / Uno Platform)
FrameworkWinUI 3 with Uno Extensions, CommunityToolkit.Mvvm
DatabaseSQLite (local sefirah.db)
Package ManagerNuGet (Directory.Packages.props centralized)
Key DependenciesCommunityToolkit.WinUI, CommunityToolkit.Mvvm, Microsoft.Extensions.Hosting, Uno.Extensions, SQLite, Windows App SDK, scrcpy (external), ADB
Build ToolMSBuild / dotnet
Test FrameworkNone detected