Open-source project
Xmarmalade/alisthelper avatar
Xmarmalade/alisthelper

alisthelper manages a server binary it does not ship, and its stable tag has not moved in twenty months

Alist Helper is an application developed using Flutter, designed to simplify the use of the desktop version of alist. It can manage alist, allowing you to easily start and stop the alist program.

2,437 stars164 forksDartGPL-3.0

At a glance

What is it?
Xmarmalade/alisthelper is a Flutter desktop launcher for a file-server program, free and GPL-3.0, whose comparison table shows it beating the commercial desktop app on exactly the two rows that need a configuration file. Its newest tag embeds a commit hash in its name, its feature list omits two of the three things it says it does, and its translation workflow will not generate a new language until you have run the app once.
Who is it for?
This is worth installing if you run that file server from a command line and want it in the tray, starting with the machine and configurable, because the two rows where this beats the commercial option are exactly the two rows that require configuration, and that is a small problem to solve once. Three things to know.
Can I use it commercially?
Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
Is it still maintained?
Activity is slowing. The repository last received commits 8 months ago.
What is it written in?
Mainly Dart, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • Xmarmalade/alisthelper2,437 ★ · -8
Star history
Repository2026-09-302026-11-15
Xmarmalade/alisthelper2.4k2.4k

-8 Stars in the last 46 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The newest tag embeds a commit hash, and the stable line is old

The release list has three entries and the newest one is not a version number.

It is a beta tag whose name contains the date and then a forty-character commit hash. That is a legitimate way to make every nightly build uniquely identifiable, and it does mean no two of them can be confused. It also means the release list cannot be sorted by version, because there is no version in the name. You have to parse the date out of the tag string, which is a thing every automated updater and every changelog generator will get wrong unless someone told it.

The gaps are the other story. The beta is from March 2026. The stable version before it is from December 2024, and the one before that from March 2024. So the last tagged stable is around twenty months behind the beta channel, and the last push to the default branch is on the same day as that beta.

There is no changelog file in the repository to reconcile any of this, so the release page is the whole version history. That is workable for three entries and will stop being workable quickly.

Read together with the dates, the picture is of a small project on a beta cadence whose stable line has been quiet for a long time. Nothing in the repository says it is finished, and the code of conduct and contribution sections are both active, but the version numbers are the only signal available.

The free helper beats the paid app on exactly two rows

The most informative thing in the readme is a comparison table with three columns and seven feature rows, and it is worth reading as a strategy rather than as marketing.

The three columns are the server program itself, this helper, and a commercial desktop application priced at eight dollars or fifty yuan. On five of the seven rows the helper and the paid application are identical: both start at boot, both start silently, both can accompany a start with something else, both have a graphical interface, and both live in the system tray.

The two rows where they differ are the interesting ones. Startup parameters and an HTTP proxy are both marked as unsupported in the commercial column, and supported in this one. On the server program's own column, those same two rows are marked as needing manual configuration.

So the pattern is exact. Everything that can be done by clicking is done by both. The two things that require writing something into a configuration file are the two things the free helper does and the paid one does not. That is a very narrow, very real gap, and it explains what this project is for better than any feature list does.

It also frames the positioning line that sits directly above the table, which is that the app is free with no tracking and no advertising, stated in three clauses without elaboration.

It manages a program it does not ship, plus two things not in the feature list

The relationship with the underlying server is worth being precise about, because the name suggests one thing and the readme says another.

There is an explicit note: this program does not include the binary files for the server, and you need to download them manually. So nothing is installed by installing this. It is a front end that starts and stops a process you obtained yourself, and every feature that depends on that process existing depends on you having fetched it.

The scope is also wider than the feature list suggests. The features are five items: automatic launching, minimising to the tray, autostart on boot with an option for silent startup, quick access to version and administrator information, and adjustable startup parameters.

Elsewhere the readme says something that the list does not cover. It says this helper also supports rclone management, and that it can mount the server as a hard drive. Those are a third external program and a filesystem-mounting capability, and neither appears anywhere in the five-item list or in the comparison table. So the table is a comparison of launchers, while the tool does two more things that the table does not mention.

The naming is unsettled in the same way. The repository description and the readme's own title use one name for the server program, while the prose repeatedly pairs it with a second name, as though the project has been renamed and the helper has been updated to cover both. The comparison table still heads its column with only the first name.

Three platform folders, one of them unsupported

Platform support is stated in one sentence with a parenthetical that does the real work.

The application is available on Windows and macOS. Linux can be built, but there is no official support yet. So Linux is a known-buildable target rather than an unknown one, and the parenthetical is doing the job of a caveat that belongs in a support matrix.

What the repository tree shows is that all three platform directories are committed: one for macOS, one for Windows, one for Linux. That is normal for a Flutter application, where each platform needs its own runner and packaging configuration, and it confirms the parenthetical is accurate rather than aspirational. Somebody can build the Linux version today, using files that are in the tree, and nobody will support them when it fails.

For a launcher whose whole job is to survive reboots and run quietly, that gap matters more than it would for an ordinary application, because a Linux user following this project's advice gets a tray icon and a boot task and no one to call.

There is no homepage recorded for the project at all, so the readme and the wiki are the entire public face of it.

Translations will not generate until you have run the app once

The translation workflow is the most interesting engineering in the repository, and it contains one step that will confuse a first-time contributor.

There are two kinds of file per language, and the distinction matters. One holds the translations that are actually used, and it is the one you edit by hand when a string is wrong. The other holds translations that the tooling believes are missing, and the instructions say explicitly that you should only update it and not treat it as source.

Adding a language is a third thing: create a new file, following a linked list of locale codes. So the three tasks, fixing a string, filling a gap and adding a language, each touch a different file.

The confusing part is the optional step at the end, which is how the generated file gets updated. The sequence is: make sure you have run the app once, then update translations through the code generator, then run the app again. The precondition is the problem. A contributor who has never run the application cannot generate anything, because generation is triggered by having run it. That is a genuine circular dependency in the onboarding path, and it is documented rather than hidden, which is more than most projects manage.

The rest of the loop is conventional and sound, and it is three commands:

shell
flutter pub get
dart run build_runner build
flutter run

Dependencies are fetched, the code generator runs, the app launches. The generator has its own configuration file committed at the root, alongside the static analysis configuration and a developer tools options file. And there is a convention for non-translatable fields: entries marked with a prefix character are informative only and are not used by the application at all.

The contributing section promises steps it does not contain

There is a structural gap in the readme that is easy to miss and worth naming.

Under the contributing heading there is a subsection titled Getting Started, and its one sentence says that if you are interested in contributing code you will need to follow these steps. Then a colon. And then the next heading, which is about running the project locally: install the development framework, fetch dependencies, run the generator, launch it. Those are the steps for a contributor to get a working copy on their own machine, not the steps for contributing code.

So the section that should route a new contributor, from an issue through a branch to a pull request, is a stub, and the actual development instructions follow instead.

The guidelines that come later are specific and mostly good: code documented and formatted to the language's own style guide, commits written and descriptive with context, and pull requests targeting the master branch with a clear summary. One of them is a requirement with nothing behind it in the visible tree. All changes should be covered by tests, and the repository's top-level listing contains no test directory.

The licence file is present, as is a code of conduct, and the readme has a second copy of itself in Simplified Chinese alongside the English one.

An empty screenshots table and a wiki in one language

Two small presentation problems sit near the top of the page and are the first things a visitor sees.

The screenshots section is a two-column table with a header row, a separator row, and nothing in it. Both cells of the header are blank and both cells of the body are blank, so the section renders as an empty box where the project's screenshots should be. Given that the application is a tray-and-window utility whose entire value is that it disappears into your desktop until you need it, screenshots would have been doing real work here.

The second is a language one. The getting-started link points at the project wiki and its label says explicitly that the wiki is in Simplified Chinese. There is no English counterpart offered, and no second link. So for anyone who reads English, the only route from the readme into anything beyond installation is the contributing section, which is the stub described earlier.

That leaves the readme itself, the English and Simplified Chinese pair of which it is one of, and the wiki. For a project that has been shipping beta builds for over a year on a twenty-month-old stable tag, the gap between what the tool does and what its documentation says about it is wider than the gap between its versions.

Editorial conclusion

This is worth installing if you run that file server from a command line and want it in the tray, starting with the machine and configurable, because the two rows where this beats the commercial option are exactly the two rows that require configuration, and that is a small problem to solve once. Three things to know. You have to fetch the server binary yourself, so this is a launcher rather than a distribution and nothing is installed by it. Linux is buildable but explicitly unsupported, despite the platform folder being committed. And if you want to help with translations, read the workflow first, because the generated file will not appear until you have run the app once, which is an odd first step to be handed.

Frequently asked questions

What is alisthelper?

A Flutter desktop application for managing and launching the alist or openlist file server, with tray minimisation, autostart on boot, a silent startup option, quick access to version and administrator information, and editable startup parameters. It is GPL-3.0 licensed and described as free with no tracking and no advertising.

Does alisthelper include the alist binary?

No. The readme states that the program does not include the binary files for the server and that you need to download them manually. That makes it a launcher and manager rather than a distribution, and every feature depends on you having fetched the process yourself.

Which platforms does alisthelper support?

Windows and macOS are available. Linux can be built but has no official support, and the repository commits a Linux platform directory alongside the macOS and Windows ones, so the build is possible today and unsupported after that.

What can alisthelper manage besides the alist server?

It also supports rclone management, and it can mount the alist or openlist target as a hard drive. Neither of those two appears in the five-item feature list or in the comparison table.

How do I add a translation to alisthelper?

Fork the repository, then either fill in the missing-translations file for an existing language without treating it as source, or correct the hand-maintained strings file, or create a new file for a new language. Updating the generated file requires having run the app once first, then the code generator, then the app again.

How do I run alisthelper from source?

Install the Flutter framework, fetch dependencies, run the code generator, then launch the app. The generator step sits between the two Flutter commands because it is what produces the translation files.

Official sources

  1. Issues
  2. License: GPL-3.0
  3. README
  4. Releases
  5. Xmarmalade/alisthelper on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/xmarmalade-alisthelper.svg)](https://hysenlabs.com/projects/xmarmalade-alisthelper)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/xmarmalade-alisthelper.svg)](https://hysenlabs.com/projects/xmarmalade-alisthelper)

Was this useful?