node-vault

Client for HashiCorp's Vault

Runs with mockssource: GitHubhomepageJavaScriptMITcommit bd429e885926

JavaScript, MIT licensed. The project labels itself: api, api client, client, hashicorp, node, node vault, nodejs and secrets.

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

node-vault v0.12.0 installed cleanly, all 99 tests pass including init and status against a mock Vault server

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
1
last tested
stars
556
forks
160
open issues
8
watchers
7
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.

Install time
under a minute
Cold machine to finish
4 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
npm test exited 0, 99 passed (97 unit + 2 integration against mock Vault HTTP API on 127.0.0.1:8200)
Model tokens used
54,047
Exact commit tested
bd429e885926
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.

      stopAllRenewals
        ✔ should stop both token and lease renewals
  99 passing (68ms)
All 99 tests pass (97 unit + 2 integration). Let me clean up the mock server:
2026-10-18T07:19:32.016609Z ERROR codex_core::tools::router: error=exec_command failed: CreateProce…
exec
/bin/sh -lc 'pkill -f "node scripts/mock-vault" 2>/dev/null || true' in /work/repo
 exited 143 in 0ms:
All 99 tests pass: 97 unit tests require no external dependencies, and 2 integration tests pass aga…
tokens used
54,047
All 99 tests pass: 97 unit tests require no external dependencies, and 2 integration tests pass aga…

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 0.5 minutes, faster than the median of the 61 comparable projects Argusic has measured.
  • Nothing broke on the way: zero errors between clone and running.
  • 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.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 62 api projects Argusic has installed and timed, node-vault was the 10th fastest to reach a running state, and 39 of 62 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.03

Topics (from GitHub)

apiapi-clientclienthashicorpnodenode-vaultnodejssecretsvault

Embed the badge

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

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

Questions

Does node-vault run?
node-vault 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 node-vault?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit bd429e885926. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test node-vault?
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 node-vault 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 node-vault need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing node-vault?
Nothing did, in the recorded run: zero errors between clone and running.
How does node-vault compare with the alternatives?
Of the 62 api projects Argusic has installed and timed, node-vault was the 10th fastest to reach a running state, and 39 of 62 reached one at all.
Where is the evidence for node-vault?
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