vandium-node

AWS Lambda framework for building functions using Node.js for API Gateway, IoT applications, and other AWS events.

Runssource: GitHubJavaScriptBSD-3-Clausecommit 339062d4bb27

JavaScript, BSD-3-Clause licensed. The project labels itself: api gateway, aws lambda, iot, jwt, lambda and serverless.

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

npm ci installs the project in about 5 seconds, the test suite passes 436/436 tests with 100% coverage, and both the README-style API builder and examples/api-gateway/handler.js return statusCode 200 with correctly parsed, type-coerced JSON bodies when invoked with a real API Gateway fixture event.

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
1
last tested
stars
383
forks
28
open issues
27
watchers
20
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 vandium-node, 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.

  • handler invoked without Lambda context: TypeError 'Cannot destructure property succeed of undefined' at lib/event_types/handler.js:390.1 minutes
  • minimal synthetic API Gateway event failed with TypeError reading 'onResponse' of undefined at lib/event_types/api/api_handler.js:2540.1 minutes
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
npm test exited 0 reporting '436 passing (1s)' with 100% nyc coverage; node /tmp/smoke.js printed 'STATUS: 200' and body {"users":["Jon Doe"],"offset":10} for the README fluent .GET().validation().handler() API; node /tmp/exmp/run.js invoked the shipped examples/api-gateway/handler.js and printed 'STATUS: 200' with body {"users":[{"firstName":"Jon","lastName":"Doe","age":42}],"offset":5}
Model tokens used
113,520
Exact commit tested
339062d4bb27
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 attempt that decided the verdict above. 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.

npm notice filename:      vandium-6.1.0.tgz
npm notice package size:  15.4 kB
npm notice unpacked size: 57.4 kB
npm notice shasum:        652a42fa384133b64450d222097e0d1c006c90ff
npm notice integrity:     sha512-nI0QafPWJK677[...]doP+SIz567/VA==
npm notice total files:   41
npm notice
vandium-6.1.0.tgz
All verification is complete. The repository installs cleanly, the full test suite passes, and real…
tokens used
113,520
All verification is complete. The repository installs cleanly, the full test suite passes, and real…

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.1 minutes, faster than the median of the 31 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 BSD-3-Clause, as reported by its host.

What did not, or is not known

  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 32 api-gateway projects Argusic has installed and timed, vandium-node was the 4th fastest to reach a running state, and 22 of 32 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.1 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 Runner1/3Runs100.000.02

Topics (from GitHub)

api-gatewayaws-lambdaiotjwtlambdaserverless

Embed the badge

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

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

Questions

Does vandium-node run?
Yes. vandium-node runs. Argusic installed and launched it on a clean machine in 0 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test vandium-node?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 339062d4bb27. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test vandium-node?
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 vandium-node take to install?
0.1 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 vandium-node need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing vandium-node?
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 vandium-node compare with the alternatives?
Of the 32 api-gateway projects Argusic has installed and timed, vandium-node was the 4th fastest to reach a running state, and 22 of 32 reached one at all.
Where is the evidence for vandium-node?
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