Choose Yoinks for the picker
Yoinks is a terminal format picker powered by yt-dlp. Its README describes pasting a URL, selecting a resolution or audio-only MP3, and saving the result to ~/Downloads. It documents keyboard and mouse controls. These are documented capabilities; our sandbox did not exercise the interactive flow.
The README places picker-bypassing flags, configurable output folders and playlist support on its roadmap. Choose Yoinks when selecting a format interactively is the feature you want. If your workflow depends on URL lists or destination controls, yt-dlp's documented command-line options provide a more direct starting point.
Our run built successfully and failed its test command
Our run on October 1, 2026, used commit 6f03720. The build log identifies Yoinks 0.3.1. Our sandbox's stored harness records installation success in 15 seconds and build success in 6 seconds. The test command exited with code 1 after 7 seconds.
For this run, the harness records command success, exit code, elapsed time, timeout status and parsed test counts. Its stored parser summaries record 5 passed, 1 failed and 6 total. Those summaries do not establish exhaustive unique test coverage. This correction uses the existing record; we performed no new execution or complete-log reconciliation.
The raw test tail names the failing subtest as "forced themes paint native border cells with the theme background" and reports "Invalid regular expression flags" with a module-loading stack. That establishes a test execution failure, but does not establish that the rendered theme was incorrect. The raw footer separately records zero skipped tests.
We did not test the interactive picker, a real media download, MP3 extraction, stream merging or operation on Windows or macOS. The supplied MrKeyoor testing methodology explains how the publisher records command outcomes and their limits. Its current text does not establish which methodology version applied to this older run.
Node compatibility needs a separate check
Our install log reports Node v18.20.8 and engine warnings for ink@7.1.0 and cli-truncate@6.1.1 requiring Node >=22. That matters because the README says Node 18+ is sufficient. The stored sandbox image label, lab-node:22, disagrees with the runtime npm reports. Installation returning zero does not settle compatibility, and the supplied tail does not prove that upgrading Node would fix the SyntaxError.
According to the README, Yoinks uses an existing yt-dlp installation or downloads its standalone binary into ~/.yoinks/bin. It finds ffmpeg on PATH, with ffmpeg-static as a bundled fallback. Our run did not verify these components through a download or conversion. Before depending on Yoinks, check your runtime against its installed dependencies and try content you have permission to save.
Footprint and audit results need different interpretations
The stored harness records 121 dependency packages and a 172 MB installed footprint, alongside a 0.4 MB checkout. These are the attached harness measurements. The raw install output contains a different package-addition figure; it does not replace the stored dependency count or establish audit coverage.
The stored audit summary records zero advisories, while the raw install tail reports one low-severity vulnerability. The supplied record does not reconcile those outputs. Scan coverage is unknown because scannedPackages is absent. Neither output proves that Yoinks is secure.
The repository scan records zero CI workflow files and no top-level tests directory. Tests nevertheless exist beside source files: the recorded test command targets src/**/*.test.ts. The directory signal therefore does not mean there are no tests.
Alternatives serve different workflows
The yt-dlp documentation includes batch-file input and configurable download paths. Use it directly when those controls matter more than the picker. It is both Yoinks' underlying downloader and a replacement for its interface. We did not compare their download success rates or runtime performance.
Cobalt's repository contains an API and web frontend. Consider it as an alternative interface when you want a web workflow. Its README limits downloading to free, publicly accessible content. The supplied extract establishes that role, not feature parity or successful deployment in our sandbox. Neither alternative was executed for this review.
Yoinks' README describes personal archiving and warns that downloading may violate platform terms. Choose content you have the right to keep before testing any downloader.
What the scores mean
The visible rubric is: 1 means substantial obstacles, 2 means material limitations, 3 means usable with caveats, 4 means strong documented support, and 5 requires broader corroboration than this single run. These are editorial assessments of the named dimension, not performance measurements. An unassessed dimension receives no number.
Setup ease receives 3 because installation and building completed, but engine warnings and the failed test command need follow-up. Documentation receives 4 because the README explains installation, controls, dependency handling, destinations and roadmap limits. Maturity receives 2 because the recorded test command failed and the scan found no CI workflows. Community remains unassessed because the independently fetched extracts do not establish maintainer responsiveness or current contributor activity.

