fredy

❤️ Fredy - [F]ind [R]eal [E]state [D]amn Eas[y] - Fredy keeps searching for new apartments, houses, and flats in Europe on platforms like ImmoScout24, Immowelt, eBay Kleinanzeigen and instantly delivers the results to you via Slack, Telegram, Email, Discord or ntfy, so you can focus on the more important things in life ;)

Runs with mockssource: GitHubhomepageJavaScriptApache-2.0commit 1d0c3d70d580

JavaScript, Apache-2.0 licensed. The project labels itself: appartment, appartments, crawler, ebay kleinanzeigen, fredy, immobilien, immobilienscout24 and immoscout24.

fredy runs, with stand-ins for the services it depends on. An Argusic agent installed it in 1 minute and hit no errors on a clean machine with no GPU, and the whole session was recorded.

Fredy backend serves UI on port 9998 with all 45 migrations applied, login authenticates admin/admin, and all 4260 offline tests pass.

What the agent ended up with on a clean machine, in its own words. How this is measured

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

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.03 (measured)
recorded runs
2
last tested
stars
1,645
forks
266
open issues
4
watchers
8
size
59 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . 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.

Install time
1 minutes
Cold machine to finish
5 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
curl -s -o /dev/null -w '%{http_code}' http://localhost:9998/ returned 200; curl -b cookies http://localhost:9998/api/login/user returned admin user; TEST_MODE=offline yarn test:offline exited 0 with 4260 passed
Model tokens used
63,156
Exact commit tested
1d0c3d70d580
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.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
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
Behaviour against real services
this run was verified against stand-in services only

The end of the recording

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

Everything worked perfectly. Here's the summary:
## Results
**Install & setup:**
- Upgraded Node.js from v18.19.1 → v22.23.5 (via `n`), enabled yarn via corepack
- Changed `conf/config.json` `sqlitepath` from `/db` → `/work/repo/db` (Docker path wouldn't work l…
- `yarn install` → all deps resolved, frontend built in 1.4s
**App launch:** Started on `localhost:9998`, ran all 45 DB migrations, UI served at `/` (200), logi…
**Tests:** `TEST_MODE=offline yarn test:offline` → **4260 passed, 33 skipped, 1 skipped file** acro…
**Lint:** `yarn lint` (oxlint) → clean, 0.11s.
No errors were encountered. The only necessary changes were the Node.js version upgrade and the con…
```
```

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

  • Installed in 1 minute.
  • 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

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.

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 byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs with mocks92.000.03
Argusic Runner1/3Runs with mocks92.000.06

Topics (from GitHub)

appartmentappartmentscrawlerebay-kleinanzeigenfredyimmobilienimmobilienscout24immoscout24immoweltnodejspuppeteerreal-estatereal-estate-searchself-hostedtelegrambotsweb-scrapingwg-gesuchtwohnungssuche

Embed the badge

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

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

Questions

Does fredy run?
fredy runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 1 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test fredy?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 1d0c3d70d580. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test fredy?
The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does fredy take to install?
1 minute in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does fredy need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing fredy?
Nothing did, in the recorded run: zero errors between clone and running.
Where is the evidence for fredy?
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.

Discussion