google-play-scraper

Node.js scraper to get data from Google Play

Runssource: GitHubJavaScriptMITcommit 20359f62469c

JavaScript, MIT licensed. The project labels itself: api, crawler, google play, nodejs and scraper.

google-play-scraper runs. An Argusic agent installed it in 0.5 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

The google-play-scraper npm module installs, its index.js exports all 12 documented methods, and all 84 tests pass against live Google Play endpoints.

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 100 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.02 (measured)
recorded runs
2
last tested
stars
3,004
forks
724
open issues
8
watchers
91
size
1 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.

Time lost to each failure while testing google-play-scraper, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • test/lib.app.js line 58 calls assertValidUrl(app.video) which fails when video is undefined2 minutes
  • mocha v12 requires Node >=20.19 but container has Node v18.19.11 minute
Install time
under a minute
Cold machine to finish
3 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
npx mocha --timeout 15000 exited 0, 84 passing
Model tokens used
89,207
Exact commit tested
20359f62469c
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

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

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

    at node:internal/main/eval_string:30:3
Node.js v18.19.1
exec
/bin/sh -lc "cd /work/repo && node --input-type=module -e \"import gplay from './index.js'; console…
 succeeded in 112ms:
memoized, clusters, category, collection, sort, age, permission, app, list, search, suggest, develo…
The module loads correctly and exports all expected methods.
Here's my report:
tokens used
89,207
The module loads correctly and exports all expected methods.
Here's my report:

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

  • Reached a running state on a clean machine, with the session recorded.
  • Installed in 0.5 minutes, faster than the median of the 61 comparable projects Argusic has measured.
  • Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

Of the 62 api projects Argusic has installed and timed, google-play-scraper was the 8th fastest to reach a running state, and 37 of 62 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • A quick evaluation: it was running 0.5 minutes after the clone.

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/3Runs100.000.02
Argusic Runner1/3Runs100.000.03

Topics (from GitHub)

apicrawlergoogle-playnodejsscraper

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/google-play-scraper.svg)](https://argusic.com/subject/google-play-scraper)

Questions

Does google-play-scraper run?
Yes. google-play-scraper runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test google-play-scraper?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 20359f62469c. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test google-play-scraper?
The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does google-play-scraper take to install?
0.5 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does google-play-scraper need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing google-play-scraper?
2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does google-play-scraper compare with the alternatives?
Of the 62 api projects Argusic has installed and timed, google-play-scraper was the 8th fastest to reach a running state, and 37 of 62 reached one at all.
Where is the evidence for google-play-scraper?
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