App Manager is a production Android package-management application rather than a data or research codebase. The source code confirms a deep, privileged management tool: it inspects installed applications, edits components/permissions/app ops, freezes and uninstalls packages, backs up and restores app data with multiple encryption schemes (AES, RSA/ECC, OpenPGP), applies profiles and batch operations, manages root/ADB execution, performs APK/tracker/VirusTotal analysis, and bundles ancillary tools such as a file manager, code editor, logcat viewer, PDF/audio viewers, and terminal. The hybrid-looking data features—VirusTotal scan caching, tracker signature datasets, usage statistics, debloat lists—are product features, not the repository's primary purpose.
Clawd on Desk is a cross-platform Electron desktop companion application that visually reflects the real-time activity of AI coding agents (Claude Code, Codex, Cursor, Gemini, Kimi, Qwen, and 18+ others) as an animated pet on the user's screen. The application integrates with each agent via hook scripts that intercept lifecycle events (thinking, working, idle, error, etc.) and post state to a local HTTP server, which drives the pet's animations, permission bubbles, and system tray presence. It provides a sophisticated permission management system with local bubble UI, remote approval via Telegram/Feishu/Slack, and session automation policies, all while supporting custom themes, Discord Rich Presence, and a mobile companion PWA. The architecture is an Electron main process orchestrating multiple renderer windows (pet, bubble, settings, dashboard, quota ring, session HUD) with IPC bridges. The state machine resolves session states from multiple agents into a single dominant visual state using priority-based resolution. The codebase is modular with factory functions, dependency injection, and pure math modules that are testable in isolation. It includes a comprehensive theme system with SVG/GIF/APNG support, a doctor/health check system, remote SSH deployment of hooks, and a recap feature for local activity tracking. The project has over 1000 test files and extensive CI/CD pipelines for Windows, macOS, and Linux packaging.
Stellar is a Shizuku-fork Android application that provides a privileged service framework enabling apps to use system-level APIs without root. The repository contains two main modules: a manager app with Jetpack Compose UI (including home dashboard, app permission management, terminal command execution, settings, and a startup wizard) and a server process that runs as a system service via app_process, managing Binder IPC, permissions, remote process creation, and Shizuku API compatibility. The manager app uses Room for persistent configuration and logs, while the server communicates with the manager and client apps through Binder and a ContentProvider bridge. The project demonstrates deep integration with Android internals (hidden APIs, ProcessObserver, UidObserver) and includes native C++ code for ADB wireless pairing via mDNS and TLS, as well as privilege drop and cgroup management. While the code is well-organized and modular in parts, it is tightly coupled to Android platform specifics and lacks automated tests, making it primarily useful as a reference for building similar privilege-escalation frameworks or for users wanting to manage Stellar on their devices.
This repository provides a full-stack demonstration of a permission management system using Spring Boot for the backend and Vue.js for the frontend. Despite its name, it does not use Apache Shiro; instead, it implements a custom, annotation-based permission control via AOP (RequiresPermissions annotation and PermissionAspect) and token-based authentication using Caffeine local cache. The backend is a monolithic Spring Boot 2.3.10 application with MyBatis for database access, serving a REST API. The frontend is a Vue 2 application (based on vueAdmin-template) with dynamic routing and ElementUI, featuring a custom directive for button-level permission checks. The system supports multi-role users, role-based menu and permission assignment, and a clean separation of concerns between backend and frontend permission enforcement. The codebase is well-structured and serves as a clear reference for implementing RBAC-like permission systems in Java+Vue projects, though it is not intended for production use without significant hardening and updates.