sohaibdevv/youtube-music and the gap between version 3.12.0 and tag v1.0.0
A lightweight, ad‑free client for streaming music from YouTube Music. No subscription required. Supports background playback, search, and custom playlists via the reverse‑engineered API.
At a glance
- What is it?
- A TypeScript Electron client that streams YouTube Music through an API Google never published, wrapped and distributed as one password-protected EXE. The code carries version 3.12.0 while the release list stops at v1.0.0, and the page documents a Windows binary the build scripts do not actually produce.
- Who is it for?
- Read this as a description of how the project is built rather than as something to run day to day. The terms of the streaming side come first: the disclaimer states the project is not affiliated with Google, holds no rights, and works by calling an API Google never published, so a session can stop working without warning and without a changelog.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 102 days ago.
- What is it written in?
- Mainly TypeScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on October 21, 2026, and from our analysis. They are not legal advice.
Star history
- sohaibdevv/youtube-music777 ★ · +1
| Repository | 2026-09-21 | 2026-10-21 |
|---|---|---|
| sohaibdevv/youtube-music | 776 | 777 |
1 Stars in the last 30 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Streaming rides on an API Google never published
The project's one-line summary credits a reverse-engineered API, and the disclaimer says the app streams audio like a browser: no downloading, no DRM bypass, not affiliated with Google, all rights belong to the owners. That pair of statements defines the shape of the whole project. Nothing at the top level points at an official client library, an SDK, or a checked-in description of the endpoints being called, so every row of the feature table depends on request shapes that Google can change without notice and without a changelog. The background playback row is the clearest case, because keeping audio alive while the window is minimized is a property of the playback surface being driven, not of anything the src directory ships. The README documents no account step, no cookie handling, and no configuration file for any of it.
package.json carries 3.12.0 while the release list stops at v1.0.0
The manifest names the package youtube-music, sets version 3.12.0, gives the app id com.github.th-ch.youtube-music, and points its repository field at pear-devs/pear-desktop with author th-ch and an email at that same handle. The code in this repository is therefore not authored from scratch under sohaibdevv, it descends from a differently named upstream whose owner fields were never rewritten. Two version numbers then sit side by side. The single release is v1.0.0, tagged youtube-music v1.0.0 on 2026-08-11, and the last push to main carries that same date with nothing committed since. A three digit internal version sitting next to a one digit tag means a reader cannot tell from either number which upstream commit a given build came from.
The download is a ZIP with its password printed beside the link
The download section points at the repository's releases/latest page, says the archive is a ZIP, and asks the reader to unzip it with a password that the same page prints a few lines above the link. A password on a ZIP gates nothing for anyone who already holds the file, and it does not authenticate the publisher either. No checksum, signature, or hash appears anywhere in the README. The feature table calls the build portable, a single EXE with no install, no registry and no leftovers, while the top level of the tree shows a full source project with electron-builder.yml and electron.vite.config.mts sitting next to package.json. So the artifact a reader receives is a build product, and the page offers no way to confirm which commit produced it or whether it was modified in transit.
The build scripts target three platforms while the page names one executable
The manifest's packaging scripts are where the real platform story sits. Two of these lines are visible in full before the file cuts off mid string:
"dist": "pnpm clean && pnpm build && pnpm electron-builder --win --mac --linux -p never",
"dist:linux": "pnpm clean && pnpm build && pnpm electron-builder --linux -p never",A third, dist:linux:deb-arm64, is present but its value stops partway through. The -p never flag tells electron-builder to produce the packages without publishing them anywhere. So one manifest can emit Windows, macOS and Linux artifacts plus an arm64 Debian package. The how to use section names a single binary and its .exe suffix, which is the Windows shape only, and the repo has no homepage to point anywhere else.
postinstall and a patches directory both run before the app opens
Two entries at the top level change what building this project means. The first is the manifest's postinstall hook, pnpm install-electron, which runs on every install of the workspace. The second is the patches directory, a set of modifications applied to dependencies, sitting alongside pnpm-lock.yaml, pnpm-workspace.yaml and renovate.json. Together they mean the build is not a plain checkout, since dependency code is patched and an install time fetch runs before electron-vite build ever starts. The same scripts wire up Playwright through pnpm playwright test with a separate tsconfig.test.json and a tests directory, and the development entry sets NODE_ENV=development with --enable-source-maps through cross-env rather than calling the bundler directly.
Seven feature rows and not one documented setting
The feature table sets out seven rows: no ads, background playback, search, local playlists described as saving queues with no tracking, a dark theme that switches automatically or manually, media keys for play, pause, next and previous, and a portable single EXE. Not one of the seven has an option documented behind it. There is no settings section, no config file name, no environment variable, and no account step, even though the manifest's own description says the desktop app includes custom plugins while the tree holds patches and vite-plugins directories. The no tracking row is the one that would need the most explanation and gets none, since a client that replays a Google service needs some way to identify itself to that service and the page never says what that is.
One release, one push date, and a changelog file in the root
The repository has a single release, v1.0.0, published 2026-08-11T18:31:34Z, and the last push to main is stamped 2026-08-11T19:26:37Z, roughly an hour later the same evening. Nothing has been committed in the fifty odd days since. The root also carries changelog.md, which is an odd file to find next to a repository whose entire release history is one tag, because there is no second version here for it to describe. Alongside it sit .oxlintrc.json and .oxfmtrc.json for linting and formatting, renovate.json for dependency updates, .devcontainer and .vscode directories for editors, and assets and web directories for the packaged front end. The project is not archived, and its public artifact count is one.
Editorial conclusion
Read this as a description of how the project is built rather than as something to run day to day. The terms of the streaming side come first: the disclaimer states the project is not affiliated with Google, holds no rights, and works by calling an API Google never published, so a session can stop working without warning and without a changelog. Before trusting any artifact, compare the manifest version against the single v1.0.0 tag, look for the checksum the README never provides, and read the postinstall hook and the patches directory before installing anything. Anyone who needs a dependable daily music setup should use an official client and pay for it.
Frequently asked questions
Does sohaibdevv/youtube-music require a YouTube Music subscription?
The one-line summary says no subscription is required and the headline asks for no premium. The same summary credits a reverse-engineered API, and the README documents no account step, no login, and no cookie handling for how the client identifies itself to YouTube Music.
What file does sohaibdevv/youtube-music tell readers to run?
The how to use section names youtube-music-free.exe inside a password protected ZIP linked from the releases/latest page. The build scripts behind it target win, mac and linux, plus a linux deb arm64 target, so the Windows executable is the only one the page describes.
Is sohaibdevv/youtube-music the same codebase as th-ch/youtube-music?
The manifest carries author th-ch, an email at that handle, and a repository field pointing at pear-devs/pear-desktop, while setting version 3.12.0 under the package name youtube-music. The only release published here is v1.0.0 from 2026-08-11, so the version numbers in the code and in the release list do not line up.
Can sohaibdevv/youtube-music download tracks or bypass DRM?
The disclaimer says the app streams audio like a browser, with no downloading and no DRM bypass, and states the project is not affiliated with Google. The README does not document any export, cache, or offline copy feature.
Does sohaibdevv/youtube-music publish a checksum for its downloads?
No checksum, signature, or hash appears in the README. The archive is password protected with the password printed on the same page, which restricts nothing for a reader who already has the file and does not verify who produced it.
Official sources
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.
[](https://hysenlabs.com/projects/sohaibdevv-youtube-music)Star history chart for your README
[](https://hysenlabs.com/projects/sohaibdevv-youtube-music)Was this useful?