Argusic could not verify that freyr-js runs. Argusic installed and launched it on a clean machine, hitting 0 errors on the way, and recorded the session.

How did Argusic test freyr-js?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit 05c059119066. 2 attempts are recorded, and the full method is on the methodology page.

What did it cost to test freyr-js?

The run that produced this verdict cost $0.27: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.

Does freyr-js need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing freyr-js?

Nothing did, in the recorded run: zero errors between clone and running.

Where is the evidence for freyr-js?

All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

freyr-js

A tool for downloading songs from music streaming services like Spotify and Apple Music.

Could not verifysource: GitHub homepageJavaScriptApache-2.0commit 05c059119066

JavaScript, Apache-2.0 licensed. The project labels itself: album, album art, apple music, artist, audio, deezer, download and itunes.

Argusic could not get freyr-js running. An Argusic agent hit no errors on a clean machine with no GPU, and the whole session was recorded.

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 20 of 100 (the mean of this project's run scores).

At a glance

verdict: Could not verify
Argusic Score: 20 / 100
cost of the verifying run: $0.27 (measured)
recorded runs: 2
last tested: 2026-09-12
stars: 2,353
forks: 154
open issues: 110
watchers: 27
size: 4 MB
created: 2020-02-25
last push: 2026-09-21

Subject data from GitHub, linked at the top of this page, refreshed 2026-09-23. Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Cold machine to finish: 39 minutes
Errors hit and fixed: 0 hit, 0 fixed with no human help
Exact commit tested: 05c059119066
Container image: sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Install time: the run did not report one
How the result was proved: runs before 2026-09-07 did not record the command used to check the result
Peak GPU memory: this ran on a CPU machine, so there was no GPU to sample
Model tokens used: not recorded for this run
Behaviour over a long run: each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Whether it works at all: this run verified nothing, so this page makes no claim either way

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

1070:                        }))(path?.match(/range\/(\d+)-(\d+)$/) ?? url.match(/range=(\d+)-(\d+)…
1553:      const url = await authHandler.getUrl;
Let me test the download path:
exec
/bin/sh -lc 'curl -s -o /dev/null -w "%{http_code}" http://localhost:36347/audio.m4a' in /work/repo
 exited 7 in 0ms:
000
The mock server is dead. Let me restart everything properly
exec
/bin/sh -lc "pkill -f \"36347\\|36348\\|mock-server\\|spotify-mock\" 2>/dev/null; sleep 1; echo \"c…
 succeeded in 859ms:
cleaned

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

Nothing broke on the way: zero errors between clone and running.
Licensed Apache-2.0, as reported by its host.
Measured 2 times, so the result is not a one-off.

What did not, or is not known

An agent with no time limit did not get it running.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested by	attempt	outcome	score	cost USD	when
Argusic Runner	2/3	Did not run	20.00	0.27	2026-09-12 08:41 UTC
Argusic Runner	1/3	Did not run	20.00	0.20	2026-09-12 08:00 UTC

Topics (from GitHub)

album album-art apple-music artist audio deezer download itunes m4a m4a-format mpeg-4 music music-streaming nodejs playlist spotify spotify-api spotify-web-api track youtube

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/freyr-js.svg)](https://argusic.com/subject/freyr-js)

Questions

Does freyr-js run?: Argusic could not verify that freyr-js runs. Argusic installed and launched it on a clean machine, hitting 0 errors on the way, and recorded the session.
How did Argusic test freyr-js?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 05c059119066. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test freyr-js?: The run that produced this verdict cost $0.27: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
Does freyr-js need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing freyr-js?: Nothing did, in the recorded run: zero errors between clone and running.
Where is the evidence for freyr-js?: All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.