client-js

The official JS client library for the Massive.com REST and WebSocket API.

Runs with mockssource: GitHubhomepageTypeScriptMITcommit d90f2bb47e55

TypeScript, MIT licensed. The project labels itself: api client, javascript, js, lib, library and websocket.

client-js runs, with stand-ins for the services it depends on. An Argusic agent installed it in 7 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

dist/main.js (261 KB) and dist/main.d.ts (1.6 MB) built; all 4 REST API methods and WebSocket client verified against a local mock server; 0 uncommitted changes remain

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.12 (measured)
recorded runs
1
last tested
stars
274
forks
75
open issues
7
watchers
10
size
8 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 client-js, 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.

  • npm run build fails - generate step requires Java (no JDK installed) and openapi-generator-cli has ESM compatibility issues on Node 182 minutes
  • npm test fails - mocha 12 uses 'with' type import syntax unsupported on Node 18 (no test files exist anyway)1 minute
  • npm ci engine warning - yargs-parser@22 needs Node ^20.19.0 but Node 18.19.1 is available
Install time
7 minutes
Cold machine to finish
7 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
node verify_final.mjs with mock HTTP server: getStocksAggregates (PASS), getStocksSnapshotTicker (PASS), getLastStocksQuote (PASS), getLastStocksTrade (PASS), websocketClient creation (PASS)
Model tokens used
229,367
Exact commit tested
d90f2bb47e55
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.

    at createScript (node:vm:250:10)
    at Object.runInThisContext (node:vm:298:10)
    at node:internal/process/execution:82:21
    at [eval]-wrapper:6:24
    at runScript (node:internal/process/execution:81:62)
    at evalScript (node:internal/process/execution:103:10)
    at node:internal/main/eval_string:30:3
Node.js v18.19.1
Everything is done. Here's the summary:
tokens used
229,367
Everything is done. Here's the summary:

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

  • Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed MIT, as reported by its host.

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.
  • Took 7 minutes to install, slower than the median of the 39 comparable projects Argusic has measured.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 40 api-client projects Argusic has installed and timed, client-js was the 24th fastest to reach a running state, and 25 of 40 reached one at all.

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 Runner1/3Runs with mocks92.000.12

Topics (from GitHub)

api-clientjavascriptjsliblibrarywebsocket

Embed the badge

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

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

Questions

Does client-js run?
client-js runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 7 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test client-js?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit d90f2bb47e55. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test client-js?
The run that produced this verdict cost $0.12: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does client-js take to install?
7 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 client-js need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing client-js?
3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does client-js compare with the alternatives?
Of the 40 api-client projects Argusic has installed and timed, client-js was the 24th fastest to reach a running state, and 25 of 40 reached one at all.
Where is the evidence for client-js?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion