A rootless AppImage package manager for installing and managing portable apps locally without sudo privileges.
AppMan is a rootless, portable package manager specifically for AppImages and other portable Linux applications. It allows users to install, update, and manage these apps entirely within their home directory without requiring sudo or system-wide installation, solving the problem of decentralized AppImage management.
Linux users who want a centralized, command-line way to manage AppImages without root access, including non-privileged users, developers testing portable apps, and those preferring user-space installations.
Developers choose AppMan for its simplicity, rootless design, and integration with the extensive AM script database, offering a reliable, community-driven alternative to manual AppImage handling while maintaining full user control over installations.
AppImage Package Manager. "AppMan" is a redistribution of "AM" Application Manager, that does not require root privileges to install and manage apps: same code, same apps... two different behavior.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Installs and manages apps entirely within the user's home directory without sudo or root privileges, using customizable paths defined during first launch.
The core manager is a single shell script that can be run from any directory with read/write permissions, making it highly portable and easy to deploy.
Supports integration with tools like aisap and sas to sandbox AppImages for enhanced security, with dedicated guides for enabling and disabling sandboxes.
Leverages a shared, AUR-inspired database of shell scripts maintained by contributors, offering a wide range of apps and community updates.
Can only manage apps locally, unlike AM which supports both local and system-wide installations, restricting its use in multi-user or server environments.
Requires core dependencies like curl, wget, and other shell utilities, which may not be present on minimal systems and add setup complexity.
The dual repository setup (AM and AppMan) is acknowledged as confusing, with issues and contributions centralized in AM, potentially fragmenting support and documentation.