CryptoBar's feedback link points at a different repository and a different owner

The feedback link points at a different repository and owner

The Feedback section is the last thing on the page, and it invites you to open an issue if you hit a problem or want a feature. The link does not point at this repository. It resolves to a different owner entirely, and to a repository whose name is the application name without the hyphens and without the platform suffix, which is the name of the app rather than the name of the repo it ships from. So the single route the page offers for reporting a bug leads away from the code you installed, and nothing on the page acknowledges the difference. Everything else is internally consistent. The install commands, the Homebrew tap and the link to the latest release all point back at the right place. The feedback link is the only outbound reference that does not, and it is the one a user is most likely to click.

Three names for one app, and the install path needs two of them to match

The application is called CryptoBar in its heading, in its launch command and in the directory name at the repository root. The repository is called crypto-bar-mac. The Homebrew cask is called crypto-bar. The single release is titled with the two words separated by a space. That is four renderings of one thing, and the documented install path depends on two of them agreeing.

brew install --cask erdwin90/cask/crypto-bar
open -a "CryptoBar"

So the first command names the app with a hyphen and the second names it without one and with a capital. A reader who assumed the two halves matched, and typed the cask name into the launch command, would be asking the system to open a bundle that does not exist under that spelling. Small thing, but it is the kind of small thing that costs a first-time user ten minutes and a search.

A configuration section listing three settings and no mechanism

The configuration section is three bullets: tracked coins, update interval, and interface layout. What it does not say is where any of them live. There is no preferences file, no menu path, no default values, no key names and no worked example. So the three things the application is said to be customisable by are precisely the three things a reader has no route to. Nothing on the page covers what happens when a price fetch fails either, or what the menu bar shows while the request is in flight, or whether the last known value stays on screen. For an application whose entire user interface is a number in a menu bar, failure behaviour is the first thing worth knowing, and an app that has simply never been observed failing looks identical to one where nothing goes wrong.

The coin list lives in the description and nowhere on the page

The repository description promises Bitcoin, Ethereum and many other coins. The feature list says only that it shows cryptocurrency prices. The configuration section refers to tracked coins without naming a single one. So the asset list exists in a field the reader sees once, in the header of the page they landed on, and appears nowhere in the page itself. For someone deciding whether this app can show the thing they care about, the documentation offers no answer at all, and the answer that does exist is not documented anywhere a reader would look for it. The page is otherwise organised sensibly, with three translations of the readme at the repository root and a features list that stays close to what is actually implemented.

One release, and eighty-six days of commits behind it

The release history shows one release, version 1.2.0, published on 2026-06-22. The last push to the main branch is dated 2026-09-16, which is eighty-six days later. So the repository has been committed to since the only version anybody can download, and the Homebrew cask, which is the recommended install path, serves that 1.2.0 build rather than anything on the branch. For an application this size that is an ordinary cadence rather than a problem. It does mean there is a gap between what is on the branch and what a user ends up running, and the page offers no way to tell which of the two you have. The project carries 1406 stars, 127 forks and no open issues, which is consistent with an application small enough that people use it quietly instead of reporting anything about it.

Two install routes, neither of which builds anything

There are two ways to install and neither involves a compiler. The first is a Homebrew cask followed by a launch command, and the second is a link to the latest release page with the instruction to download from it. There is no build-from-source section anywhere on the page, and no mention of a toolchain. That is a choice rather than an omission, and for a menu bar utility it is a defensible one, since the audience is people who want a number in their menu bar rather than people who intend to modify it. It is worth knowing that the repository does carry a directory named after the application, alongside an assets directory, so the source is present for anyone who wants it. What is missing is the paragraph telling them how to open it and what to expect when they do.

An empty two-cell table where the screenshots should be

Partway down the page, between the introduction and the features list, there is a table with two cells and nothing in either of them. No image, no caption, no link, just an empty pair of cells, in a repository that also carries an assets directory. It reads as a screenshot block that was scaffolded and never filled in, which for this particular application is the one image that would have done the most work. A menu bar app has almost no interface to describe, and a picture of what it actually looks like in the menu bar would answer the first question every prospective user has. Everything after that point is well organised: five features, three installation notes, a configuration section, a four-item tech stack naming the language, the framework, the status item and the data source, and a licence line.

Editorial conclusion

This is a small app doing one job, and whether it does that job well is not something the page will tell you, because the page documents almost nothing about behaviour. It names three settings you can change and does not say where they live, it names a coin list in the repository description and nowhere else, and it says nothing at all about what the menu bar shows when a price request fails, which for this particular application is the question that matters most. Install the cask rather than building, since that is the path the maintainer supports, and expect the release you get to be four months older than the branch. If you want to change what it tracks or how often it refreshes, expect to read the source rather than the documentation. And if you find a bug, do not follow the feedback link on the page, because it will not take you to the code you installed.

Frequently asked questions

Official sources

1. erdwin90/crypto-bar-mac on GitHub
2. Issues
3. License: MIT
4. README
5. Releases